modelcontextprotocol / modelcontextprotocol/servers
Add: AgentPass MCP Server -- cryptographic identity and trust enforcement for AI agents
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 90.5k
- Forks
- 11.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 5
Description
What
AgentPass MCP Server -- gives every AI agent a cryptographic identity with X.509 certificates, ECDSA P-256 signed actions, and graduated trust levels (L0-L4). The private key never leaves the machine.
- npm:
@proofxhq/agentpass - Install:
npx @proofxhq/agentpass - Docs: https://agentpass.co.uk/developers.html
- Website: https://agentpass.co.uk
Tools (7)
| Tool | Description |
|---|---|
register_agent |
Generate local ECDSA P-256 keys, send CSR to CA, receive signed X.509 certificate with SPIFFE SAN and OID extensions |
sign_action |
Sign an action with the agent's local private key (MCPS per-action signing) |
verify_action |
Verify a signed action server-side, confirm agent identity and check revocation |
check_trust |
Check if an agent can perform an action based on trust level (L0-L4) |
get_cert |
Get certificate details including IANA PEN 66339 OID extensions |
revoke_agent |
Permanently revoke an agent identity |
list_agents |
List all registered agents |
Standards
- IETF: draft-sharif-agent-audit-trail-01, draft-sharif-mcps-secure-mcp
- IANA PEN 66339 OID extensions for agent trust
- OWASP MCP Security Cheat Sheet Section 7
- SPIFFE-compatible URI SANs in certificates
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the proposed @proofxhq/agentpass package and the developer documentation at https://agentpass.co.uk/developers.html. Review the seven listed tools and the MCP security and certificate standards referenced in the issue. The issue does not name repository files, tests, or acceptance criteria, so the expected integration and definition of done need clarification first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100