Is com.symbaiex.www/evidence up? Live MCP status
Yes, it is up. It answered an MCP server/discover with no credential and negotiated protocol 2026-07-28.
A stock client connected with no credential and negotiated 2026-07-28. Use it.
| Outcome | usable |
|---|---|
| HTTP status | 200 |
| Protocol version | 2026-07-28 |
| Server says it is | symbaiex-evidence v1 |
| Answered in | 107 ms |
| Endpoint checked | https://www.symbaiex.com/api/agent/mcp |
| Checked |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Published, valid. A2A 1.0 shape; 1 skill; JSONRPC./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Published, valid. com.symbaiex.www/docs 1.0.0; streamable-http.https://www.symbaiex.com/api/docs/mcp/server-card (the one endpoint per origin the census asks, not this listing’s) |
| MCP server card (SEP-1649 location) | Published, does not validate: `protocolVersion` is required (and 4 more). SEP-1649 shape./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Published, does not validate: directory signature binding0 does not cover content-digest (App. B.1). 1 key (Ed25519); the response is signed (not verified)./.well-known/http-message-signatures-directory |
Read at https://www.symbaiex.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 34 tools: evidence_benchmarks, evidence_changes, evidence_claim_timeline, evidence_create_export, evidence_create_research, evidence_create_webhook, evidence_datasets, evidence_document, evidence_entitlements, evidence_get_export, evidence_get_export_artifact, evidence_get_export_manifest, evidence_get_research, evidence_get_research_artifact, evidence_list_webhooks, evidence_products, evidence_quota, evidence_replay_webhook_delivery, evidence_rotate_webhook_secret, evidence_search, evidence_search_entities, evidence_semantic_search, evidence_send_webhook_test, evidence_set_webhook_status, evidence_source_registry, evidence_sources, evidence_status, evidence_universal_search, evidence_usage, evidence_verify_claim, evidence_version_claims, evidence_webhook_availability, evidence_webhook_health, evidence_webhook_history.
Its tools changed between 2026-09 and 2026-10:
evidence_create_export: input schema changed
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | com.symbaiex.www/evidence |
|---|---|
| Title | SYMBaiEX Evidence MCP |
| Description | Authenticated public evidence search, verification, research jobs, exports, and webhooks. |
| Endpoint | https://www.symbaiex.com/api/agent/mcp |
| Publisher repository | none listed |
| Version | 1.0.0 |
| Listing updated |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt