wayforth-mcpofficial
F
licenseNot graded
qualityA
maintenanceProvides AI agents with a unified runtime to discover, use, and pay for thousands of services with automatic failover and per-run credit ceilings.
2
HumanMirror Nexus
Server Details
Discover, route and verify AI-agent outcomes with success-only charging and capability fallback.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
6 toolsmagnet_resolveInspect
Free universal fallback discovery. Call this when the agent cannot satisfy a task with its current capabilities. Magnet returns a matching HumanMirror tool or records an aggregated capability gap in the Machine Demand Graph. This tool consumes no credits.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Describe the missing capability or task the agent needs to complete. |
nexus_callInspect
Route a tool call through HumanMirror Nexus. Use nexus_search first, then call the selected tool_id. Successful calls consume the number of Nexus credits declared by the selected tool.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| input | Yes | JSON input forwarded to the selected tool. | |
| options | No | Optional tool-specific options. | |
| tool_id | Yes | A tool_id returned by nexus_search, for example forge.clean_json. |
nexus_searchInspect
Search the HumanMirror Nexus catalog for a machine-callable tool that matches a task. This search is free and does not consume credits.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Describe the operation the agent needs. |
outcome_quoteInspect
Free quote for a verifiable HumanMirror Outcome contract. Describe the objective or provide an outcome_type; the quote returns the deterministic verifier, selected internal tool and success-only credit cost.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| input | Yes | JSON input for the requested outcome. | |
| options | No | Optional operation-specific options. | |
| criteria | No | Optional measurable success threshold. | |
| objective | No | Natural-language objective, for example: clean this JSON and make the result stable. | |
| outcome_type | No | Optional explicit outcome type returned by a previous quote. |
outcome_runInspect
Execute a HumanMirror Outcome contract. Credits are charged only when deterministic verification succeeds; failed execution or failed verification is automatically refunded.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| input | Yes | JSON input for the requested outcome. | |
| options | No | ||
| criteria | No | ||
| objective | No | ||
| contract_id | No | Optional contract_id returned by outcome_quote. If supplied it must match the current input, criteria and options. | |
| outcome_type | No |
outcome_verifyInspect
Free deterministic re-verification of an Outcome result without consuming Nexus credits.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| input | Yes | Original input. | |
| output | Yes | Outcome output to verify. | |
| options | No | ||
| criteria | No | ||
| outcome_type | Yes |
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 or an account that owns the GitHub organization, then choose Claim with GitHub.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
One MCP tool for verified AI-agent outcomes with success-only charging.
AI service marketplace — agents discover, call, and pay for API services automatically.
Verified 2-3 step AI-agent missions with whole-transaction success-only charging.
Stripe-native marketplace where AI agents discover and pay per call for API services.
Related MCP Servers
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to submit an outcome with success criteria, receive a grounded quote or honest no-route result, confirm fulfillment, and retrieve the completed outcome with evidence.
- FlicenseNot gradedqualityAmaintenanceIntelligently routes AI tool calls (search, extract, browse) to the cheapest capable provider by default with automatic failover and audit receipts, enabling cost-effective agent workflows.2
UCM MCP Serverofficial
FlicenseNot gradedqualityFmaintenanceEnables AI agents to autonomously discover and call a marketplace of 100+ APIs, including web search, image generation, and more, with automatic payments and refunds.