AI agent identity, signed credentials, delegated authority and portable governance evidence. Python core and offline verifier SDKs.

Local-first, self-hosted AI agent runtime and MCP bridge with sandboxed sessions, memory, credentials, audit/replay, and a local Console.

Provides a local MCP bridge to an end-to-end encrypted personal vault, enabling connected agents to search and save memories, manage accounts and credentials, access personal information and private addresses, and honor granular user permissions.

Enables agents to set up and manage named connections to a user's own machine, keeping credentials in private local files while requiring explicit permission review. Runs locally over stdio with no hosted endpoint and preserves existing manager state.

Converts plain-language storage requests into validated Hitachi raidcom command lines and multi-step shell scripts, including ready-made provisioning recipes, command lookup, and model limit checks. It is build-only: it never connects to a storage system, runs a command, or holds credentials, returning reviewed command text for a person to execute.

Enables Claude and other MCP clients to list and query allowlisted Supabase tables, insert rows, and search, read, or create Notion pages. It ships with table allowlists, validated inputs, row limits, and an optional read-only mode that unregisters write tools, plus a mock mode for trying it without credentials.

Enables agents to reach pump.fun's full API surface — official developer routes, bonding-curve reads, Solana RPC, and unsigned trade building — by writing JavaScript against one merged OpenAPI document, using just two tools (search and execute). Model-authored code runs in a network-less sandbox, so multi-step questions resolve in a single round trip while credentials stay on the host Worker.

Turns any OpenAPI spec into a single-tool MCP server where the model writes JavaScript against a typed api object in a QuickJS sandbox, so multi-step tasks run in one round trip and only the final result reaches context. Credentials, rate limiting, retries, write gating and audit logging stay on the host, outside the sandbox.

Enables full read/write automation of AFFiNE workspaces, documents, databases, journals, and comments through MCP tools over stdio or HTTP, supporting self-hosted and AFFiNE Cloud instances as well as multi-tenant deployments where each session supplies its own domain and credentials.

Enables AI agents to reach enterprise apps such as Jira, Microsoft 365, Salesforce, FedEx and Dell TechDirect, or your own REST APIs, through a single self-hosted MCP endpoint. Each agent gets its own key with per-app, per-value grants and a confirmation step for deletes, so calls are scoped and audited without exposing app credentials.

Enables AI coding agents to read GitHub repositories, files, commits, issues, pull requests, releases, Actions, and search results through 18 read-only MCP tools. It reuses existing credentials, routes around unreliable networks, and caches responses on disk to stay within rate limits.

Enables a single owner to use private Slack app credentials with a self-hosted Streamable HTTP MCP server to read allowlisted public channel messages, inspect thread context, send event-scoped replies, and notify the owner.

Enables an MCP-compatible assistant to log in with UNC single sign-on and explore the FCEFyN virtual classroom, listing enrolled courses, retrieving course indexes and materials, and reading or searching pages, activities, and PDFs. It works read-only with the user's own credentials, without tokens, admin permissions, or downloading entire courses.

Enables AI clients to read Charles Schwab account information over local stdio, including positions, transaction history, and option chains. It is unofficial and read-only, with credentials kept on the local machine.

Enables MCP clients to retrieve invoice history, pending invoices, and billing summary counts from a SIMAR portal through read-only tools, with credentials supplied via environment variables.

Provision cloud resources from the command line and write their credentials to .env

Enables AI assistants to look up credentials such as API keys, database URLs, and service tokens by account name, and to read inbox messages like notifications, alerts, and task assignments routed to the agent, all from self-hosted infrastructure.