Capture a public web source and return a portable, signed evidence receipt.
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.
Score is being calculated. Check back soon.
elucora_attestSeal a hash you already holdInspectProve a piece of content existed at a point in time by sealing its SHA-256 hash. Use when you already hold the bytes — a model output, a tool result, a document. Elucora records that you submitted this hash and when; it does not prove where the content came from or that it is true, because Elucora never saw the source. To prove what a web source served, use elucora_capture instead. Consumes receipt quota.
| Name | Required | Description | Default |
|---|---|---|---|
| hash | Yes | SHA-256 digest of the content, written as sha256:<64 hex characters>. | |
| metadata | No | Optional signed scalar metadata. | |
| size_bytes | No | Optional size of the content, as described by the caller. | |
| content_type | No | Optional media type of the content, as described by the caller. |
elucora_captureCapture verifiable source evidenceFreeze proof of what a web source actually served, before quoting or acting on it. Returns a signed receipt that anyone can verify offline without trusting Elucora. Proves what was served and when, not that the content is true. Sends a network request to the supplied source and consumes receipt quota.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Public HTTP(S) source URL. | |
| metadata | No | Optional signed scalar metadata. | |
| selector | No | Optional text-quote or JSON Pointer selector. | |
| idempotency_key | No | Stable retry key for this capture. |
elucora_get_receiptRetrieve an Elucora receiptFetch an evidence receipt by ID: the source it covers, the exact passage or field that was sealed, the current signature result, and its transparency log and Bitcoin anchor state. Needs no credentials.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
elucora_verifyVerify an Elucora receiptCheck whether an evidence receipt is genuine and unaltered, and what source bytes it covers. Use this before relying on a receipt produced by someone else. Needs no credentials.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
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.
No comments yet. Be the first to start the discussion!
