Inrupt ESS MCP Resource Service
Inrupt ships a first-party MCP server as an ESS service. The MCP Resource Service exposes four tools that let an AI agent ask a person for consent to their Pod data, watch for the approval, verify the resulting Access Grant, and then read the granted resource. Every call is scoped to the authenticated delegator, so the agent can never exceed the rights of the user it is acting for. Approving an Access Request is deliberately NOT an MCP tool — the human must approve it in a separate interface.
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
requestAccess— Create a new Access Request for one or more resources, stored as a Verifiable Credential and reviewable by the Resource Owner. Returns the Access Request URL with status pending.checkAccessRequestStatus— Check the current status of a previously created Access Request. Returns one of pending, granted, denied or cancelled.hasMatchingAccessGrant— Verify whether a valid (active, non-revoked, non-expired) Access Grant exists for a resource with the required access modes. Returns the Access Grant URL when one matches.getResource— Retrieve the content of a resource using a valid Access Grant.
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.