Agent Passport MCP vs AtlaSent MCP Server
A side-by-side look at the Agent Passport MCP and AtlaSent MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Agent Passport MCP for security work as a local process; choose AtlaSent MCP Server for security as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Agent Passport MCP when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
list_profiles, list_tools_for_scope, identify.
Choose AtlaSent MCP Server when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ATLASENT_MODE, ATLASENT_API_KEY, ATLASENT_BASE_URL. - You want tools like
evaluate, verify_permit, deploy_service.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 65/100 · Great | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Freemium |
| Required env vars | None listed | ATLASENT_MODEATLASENT_API_KEYATLASENT_BASE_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 0 |
| Directory activity | 5 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 152 | 20 |
| Full listing | View Agent Passport MCP | View AtlaSent MCP Server |
Tools & capabilities
Agent Passport MCP tools 152
list_profilesShow available tool profiles. Set APS_PROFILE env var to limit exposed tools (e.g. APS_PROFILE=data).list_tools_for_scopeList available MCP tools filtered by delegation scope. Pass your delegation scopes to see which tools you can use. Scopes: identity, delegation, principal, reputation, coordination, communication, governance, commerce, data, gateway, network, temporal, attribution, settlement, capability, mutual-auth. Use ['*'] for all tools.identifyIdentify yourself to the coordination server. Sets your role and scopes tools accordingly.generate_keysGenerate an Ed25519 keypair for agent identity.issue_passportIssue a complete agent passport with keys, signed passport, attestation summary, and optional values floor in a single call. The server silently captures Tier 0 observed signals and computes a passport grade (0-3). Use this to onboard any agent — no npm install required.verify_issuerVerify that a passport was officially issued by AEOESS. Checks the issuer countersignature against the published AEOESS public key. Returns false for self-signed passports.get_passport_gradeQuery the attestation grade and issuance context for a passport. Returns the passport grade (0-3), flags, and evidence summary. Grade 0 = self-signed, 1 = issuer countersigned, 2 = runtime-bound, 3 = principal-bound. This is the partner-facing trust query.list_issuance_recordsList all stored issuance records with their passport grades. Shows how many passports have been issued in this session and their trust posture. Useful for monitoring issuance patterns.get_behavioral_sequenceGet the post-issuance behavioral sequence for an agent. Shows the first 10 tool calls after passport issuance. Real agents do work. Farming agents extract. This is consilium signal #2.get_my_roleGet your current role, assigned tasks, and role-specific instructions.create_task_brief[OPERATOR] Create a new task with roles, deliverables, and acceptance criteria.assign_agent[OPERATOR] Assign an agent to a role in a task. Creates a delegation automatically.- +140 more on the listing page
AtlaSent MCP Server tools 20
evaluateCall this BEFORE performing any sensitive action. Returns a Decision: `allow` (verify the returned permit_token at the execution boundary before proceeding), `deny` (you MUST NOT proceed), or `hold` (do not proceed; route for review).verify_permitCall this AFTER `evaluate` returns allow and BEFORE the protected native side effect. It verifies the permit for the presented execution context. Proceed only when `valid` is true; expired, invalid, replayed, mismatched, or error outcomes must block the action.deploy_serviceExample protected tool. Every call is authorized AND its Permit is verified by AtlaSent before the deploy runs. Denied, held, expired, replayed, mismatched, or unverifiable calls are blocked and never touch the target system.atlasent_evaluateEvaluate an action against your published AtlaSent policies. Returns allow/deny/hold/escalate with a permitToken on allow. Use this when ATLASENT_MODE=remote and you need to gate an action against your hosted policy engine. For agent.* actions the result may carry bound_payload_hash and bound_actor_id: pass them to verify_permit as payload_hash and actor_id, since the permit is bound to them.atlasent_list_policiesList all constraint bundles / policies for this organization.atlasent_list_audit_eventsRetrieve recent evaluation events from the audit log.atlasent_explain_authorityExplain why a principal currently has (or lacks) authority for a scope. Answers 'why may principal P exercise scope/action A in organization O right now?' — strictly read-only, does not change /v1-evaluate, /v1-verify-permit, or any deny/hold/allow semantics; it explains the same facts those paths already read. Every matched authority mechanism (direct_grant, delegation, role_capability) is reported as its own path entry; every excluded or ambiguous relationship is reported as its own unresolved finding.atlasent_integrity_auditAudit the organization's authority graph for internal inconsistency and return the report verbatim. Strictly read-only; changes no policy, permit, or decision. THIS IS NOT A PASS/FAIL HEALTH CHECK and the tool synthesizes no verdict of its own. Each finding carries a three-way `classification`: `defect` is a genuine inconsistency; `non_exercisable` is frequently the CORRECT, healthy state (e.g. an expired grant that is supposed to be expired) and must not be read as a failure; `unresolved` means the proposition COULD NOT BE VERIFIED and must never be treated as clean. Read `summary.audited_scope` before drawing any conclusion from an empty findings list — a short decision window is not an absence of findings. If the audit cannot complete, the server refuses rather than returning a partial report, and this tool surfaces that as an error — never an empty report.atlasent_list_permitsList issued permit tokens for audit and monitoring.atlasent_await_approvalWait for a person to approve or reject a held action in the AtlaSent console. Use the approval_request_id from a 'hold' result. This tool cannot approve anything; it only waits. If approved, it returns a permit_token that you MUST verify with verify_permit before running the action. Any other outcome (rejected, expired, timed out) means the action must not run.atlasent_lookup_actionLook up canonical action specifications from the Authorization Intelligence Library. Returns the permanent canon_id, gate flags (requires_human_approval, requires_mfa, requires_verified_actor, requires_state_snapshot), authorization pattern, risk posture, AI risk classification, regulatory mappings, evidence requirements, and the action's knowledge-graph relationships (what it requires and produces, and which frameworks / control objectives it satisfies) for every governed action type in the Canon. Use `slug` for an exact match (e.g. 'production.deploy') or `query` to describe what you want to do in plain language (e.g. 'deploy the api service to prod', 'grant admin access', 'close the books'). `query` is ranked offline against the vendored Canon and returns a `retrieval` block with `confidence` = confident | ambiguous | none — act only on `confident`; the tool never invents an action type, and a `none` result means the Canon has no such action (see the hint). Omit both to list the full Canon.atlasent_atlas_lookupLook up a canonical AtlaSent concept from the Knowledge Atlas — the compiled graph of the system's own vocabulary (Caller, Authority, Policy, Decision, Permit, Verification, Evidence, Audit Chain, Gate, Trust Root, ...). Returns the concept's canonical definition (its source-of-truth doc), its relationships (what it depends on and what depends on it), the surfaces that realize it, and its ADR / API / SDK / implementation anchors — so every AI host reasons from the same canonical knowledge instead of guessing. Use `id` for an exact concept id (e.g. 'permit', 'audit-chain', 'gate') or `query` for a case-insensitive substring search across id, term, and definition. Omit both to list every concept.- +8 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Agent Passport MCP
{
"mcpServers": {
"aeoess-agent-passport-mcp": {
"command": "npx",
"args": [
"agent-passport-system-mcp"
]
}
}
}
AtlaSent MCP Server
{
"mcpServers": {
"atlasent-mcp-server": {
"command": "npx",
"args": [
"-y",
"@atlasent/mcp-server"
],
"env": {
"ATLASENT_MODE": "YOUR_ATLASENT_MODE_HERE",
"ATLASENT_API_KEY": "YOUR_ATLASENT_API_KEY_HERE",
"ATLASENT_BASE_URL": "YOUR_ATLASENT_BASE_URL_HERE"
}
}
}
}
Frequently asked questions
Agent Passport MCP is categorized under Security and uses a local stdio subprocess. AtlaSent MCP Server belongs to Security and uses a local stdio subprocess. Pick Agent Passport MCP for security work and AtlaSent MCP Server for security.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Agent Passport MCP is listed as free. Auth: no auth required. AtlaSent MCP Server is listed as freemium — a free tier with paid plans. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add aeoess-agent-passport-mcp and atlasent-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agent Passport MCP has a quality signal of 65/100 (Great) with 5 views, 0 installs and 4 GitHub stars. AtlaSent MCP Server has 63/100 (Good) with 1 views, 0 installs and 0 GitHub stars.