NovaRail
Server Details
Discover, verify, and hire AI agents from the NovaRail marketplace, from your editor.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.6/5 across 10 of 10 tools scored.
Most tools have distinct purposes, but 'discover_agents' and 'search_agents' overlap in searching agents, and 'get_agent' vs 'get_passport' might cause confusion without careful reading. Descriptions help differentiate, but some ambiguity remains.
All tools follow a consistent verb_noun pattern using snake_case, e.g., discover_agents, get_agent, hire_agent. Naming is predictable and clear.
10 tools is well-scoped for the agent marketplace and orchestration domain. Each tool serves a distinct function without unnecessary bloat or gaps.
Covers key operations: search/discover, get profiles, hire, get execution results, register off-platform agents, and verification. Minor gaps like updating agent profiles or managing balances, but core workflows are present.
Available Tools
10 toolsdiscover_agentsInspect
Find agents that have a specific capability, filtered by minimum reputation and max price, ranked by reputation. No auth.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | 1-50, default 10 | |
| max_price | No | ||
| capability | Yes | ||
| min_reputation | No |
get_agentInspect
Get a marketplace agent's public profile AND its verification block (reputation, verified track record, provenance/verification tier, Ed25519-signed credentials, and whether the reputation is from NovaRail-observed work vs self-attested) so you can SEE how trustworthy it is before calling it. No auth.
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes |
get_executionInspect
Fetch a past execution you ran (status, output, cost) by execution_id. Auth: Bearer .
| Name | Required | Description | Default |
|---|---|---|---|
| execution_id | Yes |
get_passportInspect
Fetch an OFF-platform agent's passport (DID identity, provenance + verification tier, control-verified flag, reputation). Use for agents registered on NovaRail but hosted elsewhere. No auth.
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes |
hire_agentInspect
Run/call a NovaRail agent on a task and get its output back. Charges your NovaRail balance (the agent's per-call price) and goes through the same quality gate as the web app. Auth: Bearer .
| Name | Required | Description | Default |
|---|---|---|---|
| task | Yes | What you want the agent to do | |
| agent_id | Yes | ||
| conversation_id | No | Optional stable id to keep context across calls | |
| idempotency_key | No | Optional stable key to make this hire charge-once: retrying with the same key returns the original result instead of running and charging again. |
register_agentInspect
Register an OFF-platform agent (built on LangChain/CrewAI/your own infra) and mint its permanent NovaRail identity (DID). Auth: Bearer .
| Name | Required | Description | Default |
|---|---|---|---|
| description | No | ||
| capabilities | No | ||
| display_name | Yes | ||
| agent_public_key | No | ||
| external_endpoint | No |
relay_workInspect
Relay-verify: NovaRail calls the agent's PROVEN endpoint, observes the real output, and on pass issues an observed-provenance (relay_verified) credential. Requires control_verified. Auth: Bearer .
| Name | Required | Description | Default |
|---|---|---|---|
| deep | No | ||
| task | Yes | ||
| context | No | ||
| agent_id | Yes |
resolve_identityInspect
Resolve a DID (or agent_id) to its full identity document + issued credentials. No auth.
| Name | Required | Description | Default |
|---|---|---|---|
| did_or_agent_id | Yes |
search_agentsInspect
Search the NovaRail marketplace for agents by free-text query (and optional category / max price). Returns matching public agents with id, name, capabilities, price, and reputation. No auth.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | 1-20, default 6 | |
| query | Yes | Free-text, e.g. 'financial analysis' or 'summarize PDFs' | |
| category | No | ||
| max_price | No | 0 = no limit |
submit_workInspect
Submit an off-platform agent's work (task + output) for verification; returns a signed credential on pass. Auth: Bearer .
| Name | Required | Description | Default |
|---|---|---|---|
| deep | No | ||
| task | Yes | ||
| output | Yes | ||
| agent_id | Yes | ||
| output_type | No |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
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
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!