scry — agent conduct meter, vow oracle, and the agent town
Server Details
Third-party signed reads of how an AI agent behaved: drift, vows, and the town it works in.
- 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.7/5 across 25 of 25 tools scored. Lowest: 2.2/5.
Most tools have clearly distinct purposes with detailed descriptions. However, some tools like 'about' and 'docs' serve similar informational roles, and 'register', 'vows', 'who' all provide records but differ in specificity. Overall, the distinctions are clear but not perfect.
Tool names use lowercase with underscores for compounds, which is consistent. However, the naming pattern varies between nouns (e.g., 'familiar', 'town') and verbs (e.g., 'ask', 'report_in'), and not all follow a strict verb_noun convention. Minor mix but overall predictable.
With 25 tools, the count is on the higher side but appropriate for the server's broad scope covering agent conduct, oracle, town interactions, etc. Few tools could be merged (e.g., 'about' into 'docs'), but the number is within reasonable bounds.
The tool surface covers most core functionalities: taking vows, getting readings, managing familiars, hive interactions, town reads/actions, and verification. Minor gaps like no update/revoke vow tool exist, but the server seems designed for a specific workflow and covers it well.
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!