Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SYMBaiEX Evidence MCP

REMOTE · WWW.SYMBAIEX.COM

Authenticated public evidence search, verification, research jobs, exports, and webhooks.

Available components

0 this week 84 Trust /100

Last scanned (12 hours ago)

Scores higher than 84% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability72
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 1072 tokens (~30/item across 35 items; 34 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 36 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 0
    • Stability: 0.97 → pass security
  • 4 Nov 26 0
    • Stability: pass → 0.97 functional
  • 12 Oct 26 0
    • Stability: 0.97 → pass security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://www.symbaiex.com/api/agent/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.symbaiex.com CN=YR2,O=Let's Encrypt,C=US 27 Oct 2026 25 Jan 2027 RSA 2048 SHA256-RSA 64e290a900a0fca719450e4de50d131e052
SANs: www.symbaiex.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.symbaiex.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
symbaiex.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000
content-security-policy default-src 'self'; script-src 'self' 'nonce-C1rvC4VwqrnpJ/UXkpvbMA==' 'strict-dynamic'; script-src-elem 'self' 'nonce-C1rvC4VwqrnpJ/UXkpvbMA=='; style-src 'self' 'nonce-C1rvC4VwqrnpJ/UXkpvbMA=='; style-src-elem 'self' 'nonce-C1rvC4VwqrnpJ/UXkpvbMA==' 'sha256-47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=' 'sha256-CIxDM5jnsGiKqXs2v7NKCY5MzdR9gu6TtiMJrDw29AY=' 'sha256-441zG27rExd4/il+NvIqyL8zFx5XmyNQtE381kSkUJk=' 'sha256-nzTgYzXYDNe6BAHiiI7NNlfK8n/auuOAhh2t92YvuXo=' 'sha256-StEaX+se6YS7pqjzrzMIA0KaX9zF/8zAhvQXZAe5epY=' 'sha256-wWU/dU8CreLlh2OcTlCbLUzZkxQ/Bdo2f9+XuzLyR/0=' 'sha256-3pRED1tOXas1FXFoPb9TGCjmYe9XQsmO9OV23khV2nY='; style-src-attr 'unsafe-inline'; img-src 'self' data: blob: https:; font-src 'self'; connect-src 'self' https://oauth.telegram.org https://www.symbaiex.com https://forum.symbaiex.com https://blog.symbaiex.com https://news.symbaiex.com https://newsletter.symbaiex.com https://symbaiex.com https://*.convex.cloud wss://*.convex.cloud https://*.convex.site; object-src 'none'; base-uri 'self'; for
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer
permissions-policy camera=(), microphone=(), geolocation=(), payment=(), usb=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.symbaiex.com/api/agent/mcp Verified 200
http (plaintext) http://www.symbaiex.com/api/agent/mcp HTTPS enforced 308 https://www.symbaiex.com/api/agent/mcp
MCP tools · 34 exposed · ~1,001 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
evidence_benchmarks ~25

List public benchmark definitions and recent runs.

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

evidence_changes ~22

List recent public evidence change events.

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

evidence_claim_timeline ~37

Read the bounded public supersession timeline for a claim key.

NameTypeReqDescription
claimKeystringyes–
limitinteger––

No output schema declared.

No examples provided.

evidence_create_export ~56

Create one bounded public JSONL export job.

NameTypeReqDescription
cursorstring––
datasetIdstringyes–
formatstring––
recordLimitinteger––
selectionStrategystring––

No output schema declared.

No examples provided.

evidence_create_research ~26

Create one bounded source-cited research job.

NameTypeReqDescription
querystringyes–

No output schema declared.

No examples provided.

evidence_create_webhook ~44

Create an owner-scoped allowlisted signed webhook subscription.

NameTypeReqDescription
eventTypesarrayyes–
subscriptionKeystringyes–
urlstringyes–

No output schema declared.

No examples provided.

evidence_datasets ~34

List public dataset selection contracts and immutable snapshot provenance, coverage, freshness, and citation metrics.

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

evidence_document ~25

Read one public evidence document by its ID.

NameTypeReqDescription
documentIdstringyes–

No output schema declared.

No examples provided.

evidence_entitlements ~20

Read effective free-beta product access for the authenticated owner.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

evidence_get_export ~26

Read one owner-scoped export job status.

NameTypeReqDescription
jobIdstringyes–

No output schema declared.

No examples provided.

evidence_get_export_artifact ~28

Resolve one authenticated first-party export artifact stream.

NameTypeReqDescription
jobIdstringyes–

No output schema declared.

No examples provided.

evidence_get_export_manifest ~31

Resolve the immutable buyer-readable provenance and coverage manifest for an export.

NameTypeReqDescription
jobIdstringyes–

No output schema declared.

No examples provided.

evidence_get_research ~27

Read one owner-scoped research job status.

NameTypeReqDescription
jobIdstringyes–

No output schema declared.

No examples provided.

evidence_get_research_artifact ~29

Resolve one authenticated first-party research artifact stream.

NameTypeReqDescription
jobIdstringyes–

No output schema declared.

No examples provided.

evidence_list_webhooks ~17

List owner-scoped webhook subscriptions.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

evidence_products ~22

List current evidence API product definitions.

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

evidence_quota ~18

Read the authenticated agent's current usage quota.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

evidence_replay_webhook_delivery ~38

Replay one stored webhook event with bounded replay protection.

NameTypeReqDescription
eventKeystringyes–
subscriptionKeystringyes–

No output schema declared.

No examples provided.

evidence_rotate_webhook_secret ~29

Rotate a webhook signing secret and return it once.

NameTypeReqDescription
subscriptionKeystringyes–

No output schema declared.

No examples provided.

evidence_search ~29

Search normalized current public evidence documents.

NameTypeReqDescription
limitinteger––
querystringyes–

No output schema declared.

No examples provided.

evidence_search_entities ~29

Search normalized public evidence entities.

NameTypeReqDescription
limitinteger––
querystringyes–

No output schema declared.

No examples provided.

evidence_semantic_search ~48

Search the public corpus with feature-gated semantic enhancement and lexical fallback.

NameTypeReqDescription
idempotencyKeystringyes–
limitinteger––
querystringyes–

No output schema declared.

No examples provided.

evidence_send_webhook_test ~38

Send one signed test event to an active webhook subscription.

NameTypeReqDescription
eventTypestringyes–
subscriptionKeystringyes–

No output schema declared.

No examples provided.

evidence_set_webhook_status ~39

Pause, resume, or revoke an owner-scoped webhook subscription.

NameTypeReqDescription
statusstringyes–
subscriptionKeystringyes–

No output schema declared.

No examples provided.

evidence_source_registry ~20

Read deterministic adapter provenance, cadence, and ingestion bounds.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

evidence_sources ~22

List current active public evidence sources.

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

evidence_status ~16

Read product API availability and capability status.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

evidence_universal_search ~38

Search public evidence, editorial, news, newsletter, and forum records.

NameTypeReqDescription
limitinteger––
querystringyes–

No output schema declared.

No examples provided.

evidence_usage ~22

Read bounded authenticated usage ledger summaries.

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

evidence_verify_claim ~27

Verify one stored public claim against version-bound citations.

NameTypeReqDescription
claimIdstringyes–

No output schema declared.

No examples provided.

evidence_version_claims ~36

List public claims cited to one evidence document version.

NameTypeReqDescription
documentVersionIdstringyes–
limitinteger––

No output schema declared.

No examples provided.

evidence_webhook_availability ~20

Read whether webhook creation is currently operator-enabled.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

evidence_webhook_health ~29

Read bounded health for one owner-scoped webhook subscription.

NameTypeReqDescription
subscriptionKeystringyes–

No output schema declared.

No examples provided.

evidence_webhook_history ~34

List bounded recent deliveries for one webhook subscription.

NameTypeReqDescription
limitinteger––
subscriptionKeystringyes–

No output schema declared.

No examples provided.

Install

How do I install the SYMBaiEX Evidence MCP server?

SYMBaiEX Evidence MCP is a hosted endpoint at https://www.symbaiex.com/api/agent/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · www.symbaiex.com

# add to Claude Code
claude mcp add --transport http com-symbaiex-www-evidence 'https://www.symbaiex.com/api/agent/mcp'
Common questions

What is the SYMBaiEX Evidence MCP server?

SYMBaiEX Evidence MCP is listed in the public MCP registry as com.symbaiex.www/evidence. Authenticated public evidence search, verification, research jobs, exports, and webhooks. This page covers its hosted endpoint (https://www.symbaiex.com/api/agent/mcp).

Is the SYMBaiEX Evidence MCP server safe to use?

SYMBaiEX Evidence MCP scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the SYMBaiEX Evidence MCP server expose?

SYMBaiEX Evidence MCP exposes 34 tools: evidence_status, evidence_sources, evidence_source_registry, evidence_search, evidence_semantic_search, and 29 more. Their descriptions and schemas cost roughly 1,001 tokens of context every time the server is loaded.

Does the SYMBaiEX Evidence MCP server require authentication?

No. We connected to SYMBaiEX Evidence MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SYMBaiEX Evidence MCP server still maintained?

SYMBaiEX Evidence MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the SYMBaiEX Evidence MCP server?

VerifyMCP ran 14 checks on SYMBaiEX Evidence MCP, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.