bsv.cx
Server Details
Timestamp and verify evidence on-chain. Prove what your agent saw and when; verifying is free.
- 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
Score is being calculated. Check back soon.
Available Tools
7 toolsarchive_urlArchive a web page with an on-chain timestampInspect
Capture a web page as it looks right now — screenshot and text — and anchor a hash of that capture on-chain. Use this before relying on a page you cite, so a later edit or deletion cannot be denied. Free.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | the page to capture | |
| thorough | No | wait for lazy-loaded content; slower but better for long or image-heavy pages |
batch_timestampTimestamp many hashes in one transactionInspect
Anchor a Merkle root over many sha256 digests in a single transaction — far cheaper per item than notarizing each one. Each hash gets an inclusion proof. 10 free calls, then priced per call.
| Name | Required | Description | Default |
|---|---|---|---|
| hashes | Yes | sha256 hex digests to timestamp together |
get_archiveRetrieve an archived page captureInspect
Fetch the manifest for a previous archive_url capture: when it was taken, and its proof. Free.
| Name | Required | Description | Default |
|---|---|---|---|
| hash | Yes | the capture hash returned by archive_url |
notarize_hashTimestamp a hash on-chainInspect
Anchor a sha256 digest in a Bitcoin SV transaction, proving the content existed at this time. Send ONLY the hash — the content never leaves your machine, and bsv.cx cannot see what was hashed. Free. Idempotent: the same hash returns the same record.
| Name | Required | Description | Default |
|---|---|---|---|
| label | No | optional public note stored with the proof | |
| sha256 | Yes | sha256 hex digest of the exact bytes you want to timestamp |
service_statusCheck bsv.cx availability and your free trialInspect
Report whether anchoring is currently working and how much of the free trial remains. Call this if a tool reports something stored but not anchored.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
verifiable_fetchFetch a page with a proof of what was returnedInspect
Fetch a URL as readable text AND get a receipt anchoring a hash of the exact bytes returned, so you can later prove what the page said when you read it. 10 free calls, then priced per call.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | the page to fetch | |
| thorough | No | wait for lazy-loaded content |
verify_hashCheck an existing timestampInspect
Look up a previously notarized sha256 and return when it was timestamped and the transaction that proves it. Free, and never rate-limited into unavailability — verifying a proof must always work.
| Name | Required | Description | Default |
|---|---|---|---|
| sha256 | Yes | the sha256 hex digest to look up |
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!