A
licenseA
qualityA
maintenanceLocal zero-trust permission gateway for AI agents. Enforces policy-based tool authorization, human approvals, scoped permissions, and cryptographically verifiable audit logs.
4
5
Apache 2.0
NEUS MCP
Server Details
The trust harness for AI agents. Set what an agent can do before it acts.
Ownership verified
- Status
- Unhealthy
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- neus/network
- GitHub Stars
- 11
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
3 tool updates
- Changed
neus_proofs_check3 fields changed- added
Input schema / properties / gateIdAdded value: +{ + "type": "string" +} - added
Input schema / properties / handleAdded value: +{ + "type": "string" +} - added
Input schema / properties / namespaceAdded value: +{ + "type": "string" +}
- Changed
neus_proofs_get1 field changed- added
Input schema / properties / qHashAdded value: +{ + "type": "string" +}
- Changed
neus_secret_list1 field changed- removed
Input schema / requiredRemoved value: -[ - "walletAddress" -]
1 tool update
- Removed
neus_me
1 tool update
- Changed
neus_proofs_get2 fields changed- added
Input schema / properties / depthAdded value: +{ + "type": "number" +} - added
Input schema / properties / traverseAdded value: +{ + "enum": [ + "supersedes", + "linked", + "delegation", + "agent-identity" + ], + "type": "string" +}
4 tool updates
- Changed
neus_agent_create2 fields changed- added
Input schema / properties / returnUrlAdded value: +{ + "type": "string" +} - added
Input schema / requiredAdded value: +[ + "agentId" +]
- Changed
neus_agent_link1 field changed- added
Input schema / properties / agentIdAdded value: +{ + "type": "string" +}
- Changed
neus_proofs_get2 fields changed- added
Input schema / properties / includeAdded value: +{ + "enum": [ + "metadata", + "content" + ], + "type": "string" +} - removed
Input schema / requiredRemoved value: -[ - "identifier" -]
- Changed
neus_verify1 field changed- changed
Input schema / requiredPrevious value: -[ - "walletAddress", - "verifierIds" -]New value: +[ + "verifierIds" +]
1 tool update
- Changed
neus_agent_create1 field changed- removed
Input schema / requiredRemoved value: -[ - "agentId" -]
1 tool update
- Added
neus_agent_mount
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Runtime permission, approval, and audit layer for AI agent tool execution.
Pre-execution governance for AI agents. Deterministic PASS/FAIL/REVIEW verdicts, replayable proof.
Zero-trust gateway for AI agents: score tool calls, verify agent cards, enforce policy, audit.
Deterministic runtime safety for AI agents: scan PII, gate tool actions, verify LLM output.
Related MCP Servers
Habenulaofficial
AlicenseNot gradedqualityBmaintenanceA personal agent control harness that governs AI agents by checking every consequential action against user-defined rules, logging all actions to a tamper-evident audit chain, and providing a global kill switch. It runs as an MCP server sidecar to coding agents or standalone, keeping users in charge of what their agents can do.4AGPL 3.0- AlicenseBqualityBmaintenanceProvides AI governance and action-assurance primitives, enabling trust scoring, policy-based allow/deny decisions, risk assessment, EU AI Act compliance checks, and an emergency kill-switch for autonomous agents.659MIT
- AlicenseNot gradedqualityCmaintenanceProvides permission gates and tamper-evident audit logging for AI agent tool executions, with declarative policies, consent ladders, and hash-chained verification.MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3.1/5.0
Disambiguation3/5
Some tools have overlapping names, such as neus_verify, neus_verify_or_guide, and neus_proofs_check, which could cause confusion. However, their descriptions clarify distinct purposes (creating/refreshing proofs vs. reusing/guiding vs. checking), so the ambiguity is moderate.
Naming Consistency2/5
Naming conventions are inconsistent: some tools use noun-verb (neus_agent_create, neus_proofs_check), others use bare verbs (neus_verify), and one uses a compound (neus_verify_or_guide). The pattern is not unified, making it harder to predict tool names.
Tool Count5/5
With 12 tools, the server offers a comprehensive set without being overwhelming. The count is well-suited for the domain, covering agents, proofs, secrets, verifiers, and context without excess or deficiency.
Completeness4/5
The tool set covers key operations for agents, proofs, secrets, and verifiers. While secret management lacks an update operation and proof management relies on verify for creation, the overall functionality is comprehensive for typical use cases.