jans-tarp-mcp-server
The Janssen Project ships one real MCP server: the Janssen Tarp MCP server, which lets an AI assistant inside the Tarp browser extension register an OIDC client and drive an authorization-code flow against any OpenID Provider. It is first-party (Apache-2.0, in the JanssenProject/jans monorepo, documented in the project's own docs) but it lives under demos/ and is not published to any registry — a developer builds and runs it themselves.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Descriptor
Candidate descriptor · transport
Tools
registerOIDCClient— Registers an OIDC client using the provider's dynamic registration endpoint.startAuthFlow— Generates an authorization URL for a registered client, with PKCE and state.exchangeToken— Exchanges an authorization code for tokens and fetches userinfo.
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.
Work with this as data
Every MCP server here is available over the APIs.io API and to AI agents over MCP.