← Back to search
Search • Shortlists • Rankings • Digests • Backfill • Incident feed • MCP API
github-overpod/mcp-telegram

overpod/mcp-telegram

Connect Telegram to Claude AI — messages, media, reactions, polls, scheduled messages & more. Hosted version: mcp-telegram.com (QR login, 30 sec setup). Built on GramJS/MTProto.

JSON report • History API • Manage this server • Global feed
Status
Failing
Score
52.8
Transport
streamable-http
Tools
0

Production readiness

Verdict
Needs remediation
Current validation evidence shows operational or discovery gaps that should be fixed first.
Critical alerts
1
Production verdicts degrade quickly when critical alerts are active.

Evidence confidence

Confidence score
55.0
Based on 20 recent validations, 26 captured checks, and validation age of 65.4 hours.
Live checks captured
26
More direct checks increase trust in the current verdict.
Validation age
65.4h
Lower age means fresher evidence.

Recommended for

No recommendation profile is available yet.

Client readiness verdicts

Ready for ChatGPT custom connector
Partial
Initialize must be reachable.; tools/list must succeed.; Transport compliance should be in good shape.
Confidence: medium (55.0)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initialize • Error
  • tools_list • Error
  • transport_compliance_probe • Error
  • step_up_auth_probe • OK
  • connector_replay_probe • Missing — Frozen tool snapshots must survive refresh.
  • request_association_probe • Missing — Roots, sampling, and elicitation should stay request-scoped.
Ready for Claude remote MCP
Blocked
Initialize must succeed or cleanly request auth.; tools/list must succeed.; Transport behavior should match Claude-compatible HTTP expectations.; A useful Claude integration needs at least one exposed tool.
Confidence: medium (55.0)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initialize • Error
  • tools_list • Error
  • transport_compliance_probe • Error
Unsafe for write actions
No
Current write surface is bounded enough for cautious review.
Confidence: medium (55.0)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history
Disagreements: none
  • action_safety_probe • OK
Snapshot churn risk
Low
No material tool-surface churn detected in the latest comparison.
Confidence: medium (55.0)
Evidence provenance
Winner: history
Supporting sources: history, live_validation
Disagreements: none
  • tool_snapshot_probe • Missing
  • connector_replay_probe • Missing

Why not ready by client

ChatGPT custom connector
Partial
Remediation checklist
  • No explicit blockers recorded.
Claude remote MCP
Blocked
Remediation checklist
  • No explicit blockers recorded.
Write-safe publishing
Ready
Remediation checklist
  • No explicit blockers recorded.

Verdict traces

Production verdict
Needs remediation
Current validation evidence shows operational or discovery gaps that should be fixed first.
Confidence: medium (55.0)
Winning source: live_validation
Triggering alerts
  • validation_stale • medium • Validation evidence is stale
  • server_failing • critical • Latest validation is failing
Client verdict trace table
VerdictStatusChecksWinning sourceConflicts
openai_connectors Partial initialize, tools_list, transport_compliance_probe, step_up_auth_probe, connector_replay_probe, request_association_probe live_validation none
claude_desktop Blocked initialize, tools_list, transport_compliance_probe live_validation none
unsafe_for_write_actions No action_safety_probe live_validation none
snapshot_churn_risk Low tool_snapshot_probe, connector_replay_probe history none

Publishability policy profiles

ChatGPT custom connector publishability
Caution
Initialize must be reachable.; tools/list must succeed.; Transport compliance should be in good shape.
  • Search Fetch Only: No
  • Write Actions Present: No
  • Oauth Configured: Yes
  • Admin Refresh Required: No
  • Safe For Company Knowledge: No
  • Safe For Messages Api Remote Mcp: No
Claude remote MCP publishability
Caution
Initialize must succeed or cleanly request auth.; tools/list must succeed.; Transport behavior should match Claude-compatible HTTP expectations.; A useful Claude integration needs at least one exposed tool.
  • Search Fetch Only: No
  • Write Actions Present: No
  • Oauth Configured: Yes
  • Admin Refresh Required: No
  • Safe For Company Knowledge: No
  • Safe For Messages Api Remote Mcp: No

Compatibility fixtures

ChatGPT custom connector fixture
Degraded
Initialize must be reachable.; tools/list must succeed.; Transport compliance should be in good shape.
  • remote_http_endpoint: Passes
  • oauth_discovery: Passes
  • frozen_tool_snapshot_refresh: Passes
  • request_association: Passes
Anthropic remote MCP fixture
Degraded
Initialize must succeed or cleanly request auth.; tools/list must succeed.; Transport behavior should match Claude-compatible HTTP expectations.; A useful Claude integration needs at least one exposed tool.
  • remote_transport: Passes
  • tool_discovery: Likely to fail
  • auth_connect: Likely to fail
  • safe_write_review: Passes

Authenticated validation sessions

Latest profile
remote_mcp
Authenticated session used
✕
Public score isolation
✓
Preview endpoint
/v1/verify
CI preview endpoint
/v1/ci/preview

Public server reputation

Validation success 7d
0.0
Validation success 30d
0.0
Mean time to recover
n/a
Breaking diffs 30d
0
Registry drift frequency 30d
0
Snapshot changes 30d
0

Incident & change feed

TimestampEventDetails
May 01, 2026 12:31:46 PM UTC Latest validation: failing Score 52.8 with status failing.

Capabilities

Use-case taxonomy
development communication monitoring

Security posture

Tools analyzed
0
High-risk tools
0
Destructive tools
0
Exec tools
0
Egress tools
0
Secret tools
0
Bulk-access tools
0
Risk distribution
none

Tool capability & risk inventory

No tool inventory available from the latest validation run.

Write-action governance

Governance status
OK
Safe to publish
✓
Auth boundary
oauth_or_auth_required
Blast radius
Low
High-risk tools
0
Confirmation signals
none
Safeguard count
0

Status detail: No unsafe write-action governance gaps detected on the latest validation.

ToolRiskFlagsSafeguards
No high-risk tools were detected on the latest run.

Action-controls diff

Need at least two validation runs before diffing action controls.

Why this score?

Access & Protocol
28.81/44
Connectivity, auth, and transport expectations for common clients.
Interface Quality
14.17/56
How well the tool/resource interface communicates and behaves under automation.
Security Posture
24/36
How safely the exposed tool surface handles destructive actions, egress, execution, secrets, and risky inputs.
Reliability & Trust
13.67/24
Operational stability, consistency, and trustworthiness over time.
Discovery & Governance
19.25/28
How well the server is documented, listed, and governed in public registries.
Adoption & Market
3.62/8
Adoption clues and public evidence that the server is intended for external use.

Algorithmic score breakdown

Auth Operability
2/4
Measures whether auth discovery and protected access behave predictably for clients.
Error Contract Quality
0.7/4
Grades machine-readable error structure, status alignment, and remediation hints.
Rate-Limit Semantics
2/4
Checks whether quota/throttle responses are deterministic and automation-friendly.
Schema Completeness
0/4
Completeness of tool descriptions, parameter docs, examples, and schema shape.
Backward Compatibility
4/4
Stability score across tool schema/name drift relative to prior validations.
SLO Health
0.5/4
Availability, latency, and burst-failure profile across recent validation history.
Security Hygiene
2/4
HTTPS posture, endpoint hygiene, and response-surface hardening checks.
Task Success
1.7/4
Can an agent reliably initialize, enumerate tools, and execute core MCP flows?
Trust Confidence
2/4
Confidence-adjusted reliability score that penalizes low evidence volume.
Abuse/Noise Resilience
2.5/4
How well the server preserves core behavior in the presence of noisy traffic patterns.
Prompt Contract
2/4
Quality of prompt metadata, argument shape, and prompt discoverability for clients.
Resource Contract
2/4
How completely resources and resource templates describe URIs, types, and usage shape.
Discovery Metadata
4/4
Homepage, docs, icon, repository, support, and license coverage for directory consumers.
Registry Consistency
2/4
Agreement between stored registry metadata, live server-card data, and current validation output.
Installability
3.3/4
How cleanly a real client can connect, initialize, enumerate tools, and proceed through auth.
Session Semantics
0/4
Determinism and state behavior across repeated MCP calls, including sticky-session surprises.
Tool Surface Design
0/4
Naming clarity, schema ergonomics, and parameter complexity across the tool surface.
Result Shape Stability
0/4
Stability of declared output schemas across validations, with penalties for drift or missing shapes.
OAuth Interop
4/4
Depth and client compatibility of OAuth/OIDC metadata beyond the minimal protected-resource check.
Recovery Semantics
0.5/4
Whether failures include actionable machine-readable next steps such as retry or upgrade guidance.
Maintenance Signal
3.8/4
Versioning, update recency, and historical validation cadence that indicate active stewardship.
Adoption Signal
2/4
Directory presence and distribution clues that suggest the server is intended for external use.
Freshness Confidence
3/4
Confidence that recent validations are current enough and dense enough to trust operationally.
Transport Fidelity
3.5/4
Whether declared transport metadata matches the observed endpoint behavior and response formats.
Spec Recency
2/4
How close the server’s claimed MCP protocol version is to the latest known public revision.
Session Resume
3/4
Whether Streamable HTTP session identifiers and resumed requests behave cleanly for real clients.
Step-Up Auth
4/4
Whether OAuth metadata and WWW-Authenticate challenges support granular, incremental consent instead of broad upfront scopes.
Transport Compliance
0/4
Checks session headers, protocol-version enforcement, session teardown, and expired-session behavior.
Utility Coverage
2/4
Signals support for completions, pagination, and task-oriented utility surfaces that larger clients increasingly expect.
Advanced Capability Coverage
2/4
Coverage of newer MCP surfaces like roots, sampling, elicitation, structured output, and related metadata.
Connector Publishability
1.6/4
How ready the server looks for client catalogs and managed connector programs.
Tool Snapshot Churn
0/4
Stability of the tool surface across recent validations, including add/remove and output-shape drift.
Connector Replay
3/4
Whether a previously published frozen connector snapshot would remain backward compatible after the latest tool refresh.
Request Association
3/4
Whether roots, sampling, and elicitation appear tied to active client requests instead of arriving unsolicited on idle sessions.
Interactive Flow Safety
3/4
Whether prompts and docs steer users toward safe auth flows instead of pasting secrets directly.
Action Safety
3/4
Risk-weighted view of destructive, exec, egress, and confirmation semantics across the tool surface.
Official Registry Presence
3/4
Whether the server appears directly or indirectly in the official MCP registry.
Provenance Divergence
4/4
How closely official registry metadata, the live server card, and public repo/package signals agree with each other.
Safety Transparency
2/4
Clarity of docs, auth disclosure, support links, and other trust signals visible to integrators.
Tool Capability Clarity
0/4
How clearly the tool surface communicates whether each action reads, writes, deletes, executes, or exports data.
Destructive Operation Safety
3/4
Penalizes delete/revoke/destroy style tools unless auth and safeguards reduce blast radius.
Egress / SSRF Resilience
3/4
Assesses arbitrary URL fetch, crawl, webhook, and remote-request exposure on the tool surface.
Execution / Sandbox Safety
4/4
Evaluates shell, code, script, and command-execution exposure and whether that surface appears contained.
Data Exfiltration Resilience
3/4
Assesses export, dump, backup, and bulk-read behavior against the surrounding auth and safeguard signals.
Least Privilege Scope
4/4
Rewards scoped auth metadata and penalizes broad or missing scopes around privileged tools.
Secret Handling Hygiene
3/4
Assesses secret-bearing tools, token leakage risk, and whether the public surface avoids obvious secret exposure.
Supply Chain Signal
0.5/4
Public metadata signal for repository, changelog, license, versioning, and recency that supports supply-chain trust.
Input Sanitization Safety
0/4
Penalizes risky freeform string inputs when schemas do not constrain URLs, code, paths, queries, or templates.
Tool Namespace Clarity
0/4
Measures naming uniqueness and ambiguity across the tool namespace to reduce collision and confusion risk.

Compatibility profiles

OpenAI Connectors
66.7
partial
Initialize must be reachable.; tools/list must succeed.; Transport compliance should be in good shape.
Connector URL: https://mcp-telegram.com
# Complete OAuth in the client when prompted.
# Server: github-overpod/mcp-telegram
Claude Desktop
33.3
blocked
Initialize must succeed or cleanly request auth.; tools/list must succeed.; Transport behavior should match Claude-compatible HTTP expectations.; A useful Claude integration needs at least one exposed tool.
{
  "mcpServers": {
    "mcp-telegram": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp-telegram.com"]
    }
  }
}
Smithery
40.0
blocked
Tool discovery must succeed.; Initialize should work before execution.; Machine-readable failure semantics should be present.
smithery mcp add "https://mcp-telegram.com"
Generic Streamable HTTP
50.0
blocked
Initialize must succeed.; tools/list must succeed.; Session behavior should be predictable.
curl -sS https://mcp-telegram.com -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'

Actionable remediation

SeverityRemediationWhy it mattersRecommended action
Critical Ensure tools/list succeeds consistently Tools discovery is the minimum viable contract for most MCP clients and directories. Make tools/list succeed unauthenticated when possible, or document the auth flow in the server card.
Playbook
  • Make `tools/list` deterministic across repeated calls.
  • Document or relax auth requirements for discovery routes.
  • Check that tool names, descriptions, and schemas remain stable across deploys.
Critical Make initialize deterministic and client-friendly If initialize fails or requires undocumented auth, many MCP clients cannot connect. Allow initialize to succeed consistently, or return a deterministic auth-required response with clear metadata.
Playbook
  • Allow `initialize` to succeed unauthenticated when possible.
  • If auth is required, return a deterministic auth-required response and matching metadata.
  • Retest against `https://mcp-telegram.com` from a clean client session.
Critical Respond to latest validation is failing Core MCP flows did not validate successfully on the latest run. Fix the failing checks first, then revalidate to confirm the recovery path.
Playbook
  • Fix the failing checks first.
  • Review the latest incident feed and validation diff for the first regression.
  • Revalidate once the remediation lands.
High Align session and protocol behavior with Streamable HTTP expectations Clients increasingly rely on MCP-Protocol-Version, session teardown, and expired-session semantics. Align MCP-Protocol-Version, MCP-Session-Id, DELETE teardown, and expired-session handling with the transport spec.
Playbook
  • Return `Mcp-Session-Id` and `Mcp-Protocol-Version` headers consistently on streamable HTTP responses.
  • Honor `DELETE` session teardown and return `404` when a deleted session is reused.
  • Reject invalid protocol-version headers with `400 Bad Request`.
High Associate roots, sampling, and elicitation with active client requests Modern MCP guidance expects roots, sampling, and elicitation traffic to be tied to an active client request instead of arriving unsolicited on idle sessions. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
High Keep connector refreshes backward compatible Managed connector clients freeze tool snapshots, so removed tools, new required args, and breaking output changes can break published integrations after refresh. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
High Publish a complete server card Missing or incomplete server-card metadata weakens discovery, documentation, and trust signals. Serve /.well-known/mcp/server-card.json and include tools, prompts/resources, homepage, and support links.
Playbook
  • Publish `/.well-known/mcp/server-card.json`.
  • Include homepage, repository, support, tools, prompts/resources, and auth metadata.
  • Revalidate the server after publishing the card.
Medium Adopt a current MCP protocol revision Older protocol revisions reduce compatibility with newer clients and registry programs. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Close connector-publishing gaps Connector catalogs care about protocol recency, session behavior, auth clarity, and tool-surface stability. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Publish OpenID configuration OIDC metadata improves token validation and client compatibility. Expose /.well-known/openid-configuration with issuer, jwks_uri, and supported grants.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Raise Adoption & Market score Adoption clues and public evidence that the server is intended for external use. Increase external documentation and directory coverage so users can discover and evaluate the server.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Raise Interface Quality score How well the tool/resource interface communicates and behaves under automation. Improve schemas, error contracts, and recovery messages so agents can reason about the surface automatically.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Reduce tool-surface churn Frequent add/remove or output-shape drift makes published connectors and cached tool snapshots brittle. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Repair prompts/list or stop advertising prompts Prompt metadata should either work live or be removed from the advertised capability set. Only advertise prompts if prompts/list works and prompt arguments are documented.
Playbook
  • Only advertise prompts that are actually accessible.
  • Add prompt descriptions and argument docs.
  • Run a live `prompts/list` check after any prompt changes.
Medium Repair resources/list or stop advertising resources Resource metadata should either work live or be removed from the advertised capability set. Only advertise resources if resources/list works and resources expose stable URIs/types.
Playbook
  • Only advertise resources with stable URIs and read semantics.
  • Add MIME/type hints where possible.
  • Run a live `resources/list` and `resources/read` check after updates.
Medium Respond to validation evidence is stale Latest validation is 65.4 hours old. Trigger a fresh validation run or increase scheduler priority for this server.
Playbook
  • Queue a new validation run now.
  • Inspect whether the scheduler priority should be raised for this server.
  • Do not rely on stale evidence for production decisions.
Medium Support resumable HTTP sessions cleanly Modern MCP clients increasingly expect resumable session behavior on streamable HTTP transports. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Low Expose modern utility surfaces like completions, pagination, or tasks Utility coverage improves interoperability with larger clients and long-lived agent workflows. Expose completions, pagination, and task metadata where supported so larger clients can plan and resume work safely.
Playbook
  • Advertise `completions`, pagination cursors, and `tasks` only when they are actually supported.
  • Return `nextCursor` on large list operations when pagination is available.
  • Document task support and whether it requires step-up auth.
Low Publish newer MCP capability signals Roots, sampling, elicitation, structured outputs, and related metadata improve client understanding and ranking. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Low Publish or reconcile the server in the official MCP registry Official registry presence improves discovery confidence and cross-source consistency. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.

Point loss breakdown

ComponentCurrentPoints missing
Transport Compliance 0/4 -4.0
Tool Surface Design 0/4 -4.0
Tool Snapshot Churn 0/4 -4.0
Tool Namespace Clarity 0/4 -4.0
Tool Capability Clarity 0/4 -4.0
Session Semantics 0/4 -4.0
Schema Completeness 0/4 -4.0
Result Shape Stability 0/4 -4.0
Input Sanitization Safety 0/4 -4.0
SLO Health 0.5/4 -3.5
Recovery Semantics 0.5/4 -3.5
Dependency Supply Chain Signal 0.5/4 -3.5

Validation diff

Score delta
0
Summary changed
no
Tool delta
0
Prompt delta
0
Auth mode changed
no
Write surface expanded
no
Protocol regressed
no
Registry drift changed
no

Regressed checks: none

Improved checks: none

ComponentPreviousLatestDelta
No component deltas between the latest two runs.

Tool snapshot diff & changelog

Need at least two validation runs before building a tool changelog.

Connector replay

Status
Missing
Backward compatible
✕
Would break after refresh
✕
Added tools
none
Removed tools
none
Additive output changes
none
Required-argument replay breaks
ToolAdded required argsRemoved required args
No required-argument replay breaks detected.
Output-schema replay breaks
ToolRemoved propertiesAdded properties
No output-schema replay breaks detected.

Transport compliance drilldown

Probe status
Error
Transport
streamable-http
Session header
no
Protocol header
no
Bad protocol response
404
DELETE teardown
n/a
Expired session retry
n/a
Last-Event-ID visible
no

Issues: missing_protocol_header, bad_protocol_not_rejected

Request association

Status
Missing
Advertised capabilities
none
Observed idle methods
none
Violating methods
none
Probe HTTP status
n/a
Issues
none

Utility coverage

Probe status
Missing
Completions
not detected
Completion probe target: none
Pagination
not detected
No nextCursor evidence.
Tasks
Missing
Advertised: no

Benchmark tasks

Benchmark taskStatusEvidence
Discover tools Likely to fail
  • initialize • Error
  • tools_list • Error
Read-only fetch flow Likely to fail
  • resource_read • Missing
  • read_only_tool_surface • Missing
OAuth-required connect Passes
  • oauth_protected_resource • OK
  • step_up_auth_probe • OK
Safe write flow with confirmation Passes
  • action_safety_probe • OK

Registry & provenance divergence

Probe status
OK
Direct official match
no
Drift fields
none
FieldRegistryLive server card
Titlen/an/a
Versionn/an/a
Homepagen/an/a

Active alerts

Aliases & registry graph

IdentifierSourceCanonicalScore
github-overpod/mcp-telegram github_topic_registry yes 52.82
github-mcp-telegram/mcp-telegram-cloud github_topic_registry no n/a

Alias consolidation

Canonical identifier
github-overpod/mcp-telegram
Duplicate aliases
1
Registry sources
github_topic_registry
Remote URLs
https://mcp-telegram.com
Homepages
https://mcp-telegram.com
Source disagreements
FieldWhat differsObserved values
Registry identifier Different registry-specific identifiers resolve to the same canonical server record here. github_topic_registry:mcp-telegram/mcp-telegram-cloud github_topic_registry:overpod/mcp-telegram

Install snippets

Openai Connectors
Connector URL: https://mcp-telegram.com
# Complete OAuth in the client when prompted.
# Server: github-overpod/mcp-telegram
Claude Desktop
{
  "mcpServers": {
    "mcp-telegram": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp-telegram.com"]
    }
  }
}
Smithery
smithery mcp add "https://mcp-telegram.com"
Generic Http
curl -sS https://mcp-telegram.com -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'

Agent access & tool surface

Live server tools
No live tool surface captured yet.
Observed from the latest live validation against https://mcp-telegram.com. This is the target server surface, not Verify's own inspection tools.
Live capability counts
0 tools • 0 prompts • 0 resources
Counts come from the latest tools/list, prompts/list, and resources/list checks.
Inspect with Verify
search_servers recommend_servers get_server_report compare_servers
Use Verify itself to search, recommend, compare, and fetch the full report for github-overpod/mcp-telegram.
Direct machine links
JSON report • Compare this server • Verify MCP API

Claims & monitoring

Server ownership

No verified maintainer claim recorded.

Watch subscriptions
0
Teams: none

Alert routing

Active watches
0
Generic webhooks
0
Slack routes
0
Teams routes
0
Email routes
0
WatchTeamChannelsMinimum severity
No active watch destinations.

Maintainer analytics

Validation Run Count
20
Average Latency Ms
4124.07
Healthy Run Ratio Recent
0.0
Registry Presence Count
2
Active Alert Count
2
Watcher Count
0
Verified Claim
False
Taxonomy Tags
development, communication, monitoring
Score Trend
52.82, 52.82, 52.82, 52.82, 52.82, 52.82, 52.82, 52.82, 52.82, 52.82
Remediation Count
20
High Risk Tool Count
0
Destructive Tool Count
0
Exec Tool Count
0

Maintainer response quality

Score
33.33
Verified claim
✕
Support contact
✓
Changelog present
✕
Incident notes present
✕
Tool changes documented
✓
Annotation history
✕
Annotation count
0

Maintainer annotations

No maintainer annotations have been recorded yet.

Maintainer rebuttals & expected behavior

No maintainer rebuttals or expected-behavior overrides are recorded yet.

Latest validation evidence

Latest summary
Failing
Validation profile
remote_mcp
Started
May 01, 2026 12:31:41 PM UTC
Latency
4098.4 ms

Failures

Checks

CheckStatusLatencyEvidence
action_safety_probe OK n/a No high-risk write, destructive, or exec tools detected.
advanced_capabilities_probe Missing n/a No advanced MCP capability signals detected.
connector_publishability_probe Error n/a Publishability blockers: initialize, tools list, protocol version, transport compliance, +3 more.
connector_replay_probe Missing n/a No connector replay evidence recorded.
determinism_probe Missing n/a tools list unavailable
initialize Error 505.2 ms Client error '404 Not Found' for url 'https://mcp-telegram.com' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
interactive_flow_probe OK n/a Check completed
oauth_authorization_server OK 156.5 ms authorization_endpoint, code_challenge_methods_supported, grant_types_supported, issuer
oauth_protected_resource OK 482.4 ms 1 authorization server(s)
official_registry_probe Warning n/a Check completed
openid_configuration Error 154.3 ms Client error '404 Not Found' for url 'https://mcp-telegram.com/.well-known/openid-configuration' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
probe_noise_resilience OK 505.1 ms Fetched https://mcp-telegram.com/robots.txt
prompt_get Missing n/a not advertised
prompts_list Missing 496.2 ms Client error '404 Not Found' for url 'https://mcp-telegram.com' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
protocol_version_probe Missing n/a No protocol version was advertised.
provenance_divergence_probe OK n/a Check completed
request_association_probe Missing n/a No request-association capabilities were advertised.
resource_read Missing n/a not advertised
resources_list Missing 489.7 ms Client error '404 Not Found' for url 'https://mcp-telegram.com' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
server_card Error 493.1 ms Client error '404 Not Found' for url 'https://mcp-telegram.com/.well-known/mcp/server-card.json' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
session_resume_probe Missing n/a no session id
step_up_auth_probe OK n/a Scopes=mcp:read.
tool_snapshot_probe Missing n/a no tools
tools_list Error 475.8 ms Client error '404 Not Found' for url 'https://mcp-telegram.com' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
transport_compliance_probe Error 157.9 ms Issues: missing protocol header, bad protocol not rejected (bad protocol=404).
utility_coverage_probe Missing 158.0 ms No completions evidence; no pagination evidence; tasks missing.

Raw evidence view

Show raw JSON evidence 
{
  "checks": {
    "action_safety_probe": {
      "details": {
        "auth_present": true,
        "confirmation_signals": [],
        "safeguard_count": 0,
        "summary": {
          "bulk_access_tools": 0,
          "capability_distribution": {},
          "destructive_tools": 0,
          "egress_tools": 0,
          "exec_tools": 0,
          "high_risk_tools": 0,
          "risk_distribution": {
            "critical": 0,
            "high": 0,
            "low": 0,
            "medium": 0
          },
          "secret_tools": 0,
          "tool_count": 0
        }
      },
      "latency_ms": null,
      "status": "ok"
    },
    "advanced_capabilities_probe": {
      "details": {
        "capabilities": {
          "completions": false,
          "elicitation": false,
          "prompts": false,
          "resource_links": false,
          "resources": false,
          "roots": false,
          "sampling": false,
          "structured_outputs": false
        },
        "enabled": [],
        "enabled_count": 0,
        "initialize_capability_keys": []
      },
      "latency_ms": null,
      "status": "missing"
    },
    "connector_publishability_probe": {
      "details": {
        "blockers": [
          "initialize",
          "tools_list",
          "protocol_version",
          "transport_compliance",
          "server_card",
          "tool_surface",
          "auth_flow"
        ],
        "criteria": {
          "action_safety": true,
          "auth_flow": false,
          "connector_replay": true,
          "initialize": false,
          "protocol_version": false,
          "remote_transport": true,
          "request_association": true,
          "server_card": false,
          "session_resume": true,
          "step_up_auth": true,
          "tool_surface": false,
          "tools_list": false,
          "transport_compliance": false
        },
        "high_risk_tools": 0,
        "tool_count": 0,
        "transport": "streamable-http"
      },
      "latency_ms": null,
      "status": "error"
    },
    "connector_replay_probe": {
      "details": {
        "reason": "no_tools"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "determinism_probe": {
      "details": {
        "reason": "tools_list_unavailable"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "initialize": {
      "details": {
        "error": "Client error '404 Not Found' for url 'https://mcp-telegram.com'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "headers": {
          "content-type": "text/plain; charset=UTF-8"
        },
        "http_status": 404,
        "payload": {},
        "url": "https://mcp-telegram.com"
      },
      "latency_ms": 505.17,
      "status": "error"
    },
    "interactive_flow_probe": {
      "details": {
        "oauth_supported": true,
        "prompt_available": false,
        "risk_hits": [],
        "safe_hits": []
      },
      "latency_ms": null,
      "status": "ok"
    },
    "oauth_authorization_server": {
      "details": {
        "headers": {
          "content-type": "application/json"
        },
        "http_status": 200,
        "payload": {
          "authorization_endpoint": "https://mcp-telegram.com/oauth/authorize",
          "code_challenge_methods_supported": [
            "S256"
          ],
          "grant_types_supported": [
            "authorization_code",
            "refresh_token"
          ],
          "issuer": "https://mcp-telegram.com",
          "registration_endpoint": "https://mcp-telegram.com/oauth/register",
          "response_types_supported": [
            "code"
          ],
          "revocation_endpoint": "https://mcp-telegram.com/oauth/revoke",
          "scopes_supported": [
            "mcp:read"
          ],
          "token_endpoint": "https://mcp-telegram.com/oauth/token",
          "token_endpoint_auth_methods_supported": [
            "none",
            "client_secret_post"
          ]
        },
        "url": "https://mcp-telegram.com/.well-known/oauth-authorization-server"
      },
      "latency_ms": 156.5,
      "status": "ok"
    },
    "oauth_protected_resource": {
      "details": {
        "headers": {
          "content-type": "application/json"
        },
        "http_status": 200,
        "payload": {
          "authorization_servers": [
            "https://mcp-telegram.com"
          ],
          "bearer_methods_supported": [
            "header"
          ],
          "resource": "https://mcp-telegram.com",
          "scopes_supported": [
            "mcp:read"
          ]
        },
        "url": "https://mcp-telegram.com/.well-known/oauth-protected-resource"
      },
      "latency_ms": 482.4,
      "status": "ok"
    },
    "official_registry_probe": {
      "details": {
        "direct_match": false,
        "official_identifiers": [
          "ai.bluenexus/universal-mcp",
          "io.github.RobThePCGuy/rag-vault",
          "io.github.isamu/mulmocast-vision",
          "app.getdialer/dialer",
          "io.github.lukisch/n8n-manager-mcp",
          "ai.smithery/Funding-Machine-ghl-mcp-fundingmachine",
          "io.github.MR901/mcp-plots",
          "io.github.MrCartographer/cartography-mcp-server",
          "io.github.kar69-96/agentpay",
          "com.onkernel/kernel-mcp-server"
        ],
        "official_peer_count": 10,
        "registry_source": "github_topic_registry"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "openid_configuration": {
      "details": {
        "error": "Client error '404 Not Found' for url 'https://mcp-telegram.com/.well-known/openid-configuration'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "url": "https://mcp-telegram.com/.well-known/openid-configuration"
      },
      "latency_ms": 154.27,
      "status": "error"
    },
    "probe_noise_resilience": {
      "details": {
        "headers": {
          "content-type": "text/plain; charset=UTF-8"
        },
        "http_status": 404,
        "url": "https://mcp-telegram.com/robots.txt"
      },
      "latency_ms": 505.11,
      "status": "ok"
    },
    "prompt_get": {
      "details": {
        "reason": "not_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "prompts_list": {
      "details": {
        "error": "Client error '404 Not Found' for url 'https://mcp-telegram.com'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "headers": {
          "content-type": "text/plain; charset=UTF-8"
        },
        "http_status": 404,
        "payload": {},
        "reason": "not_supported",
        "url": "https://mcp-telegram.com"
      },
      "latency_ms": 496.21,
      "status": "missing"
    },
    "protocol_version_probe": {
      "details": {
        "latest_known_version": "2025-11-25",
        "reason": "no_protocol_version",
        "validator_protocol_version": "2025-03-26"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "provenance_divergence_probe": {
      "details": {
        "direct_official_match": false,
        "drift_fields": [],
        "metadata_document_count": 1,
        "registry_homepage": null,
        "registry_repository": null,
        "registry_title": null,
        "registry_version": null,
        "server_card_homepage": null,
        "server_card_repository": null,
        "server_card_title": null,
        "server_card_version": null
      },
      "latency_ms": null,
      "status": "ok"
    },
    "request_association_probe": {
      "details": {
        "reason": "no_request_association_capabilities_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "resource_read": {
      "details": {
        "reason": "not_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "resources_list": {
      "details": {
        "error": "Client error '404 Not Found' for url 'https://mcp-telegram.com'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "headers": {
          "content-type": "text/plain; charset=UTF-8"
        },
        "http_status": 404,
        "payload": {},
        "reason": "not_supported",
        "url": "https://mcp-telegram.com"
      },
      "latency_ms": 489.7,
      "status": "missing"
    },
    "server_card": {
      "details": {
        "error": "Client error '404 Not Found' for url 'https://mcp-telegram.com/.well-known/mcp/server-card.json'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "url": "https://mcp-telegram.com/.well-known/mcp/server-card.json"
      },
      "latency_ms": 493.05,
      "status": "error"
    },
    "session_resume_probe": {
      "details": {
        "protocol_version": null,
        "reason": "no_session_id",
        "resume_expected": false,
        "transport": "streamable-http"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "step_up_auth_probe": {
      "details": {
        "auth_required_checks": [],
        "broad_scopes": [],
        "challenge_headers": [],
        "minimal_scope_documented": true,
        "oauth_present": true,
        "scope_specificity_ratio": 1.0,
        "step_up_signals": [],
        "supported_scopes": [
          "mcp:read"
        ]
      },
      "latency_ms": null,
      "status": "ok"
    },
    "tool_snapshot_probe": {
      "details": {
        "reason": "no_tools"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "tools_list": {
      "details": {
        "error": "Client error '404 Not Found' for url 'https://mcp-telegram.com'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "headers": {
          "content-type": "text/plain; charset=UTF-8"
        },
        "http_status": 404,
        "payload": {},
        "url": "https://mcp-telegram.com"
      },
      "latency_ms": 475.76,
      "status": "error"
    },
    "transport_compliance_probe": {
      "details": {
        "bad_protocol_error": null,
        "bad_protocol_headers": {
          "content-type": "text/plain; charset=UTF-8"
        },
        "bad_protocol_payload": {},
        "bad_protocol_status_code": 404,
        "delete_error": null,
        "delete_status_code": null,
        "expired_session_error": null,
        "expired_session_status_code": null,
        "issues": [
          "missing_protocol_header",
          "bad_protocol_not_rejected"
        ],
        "last_event_id_visible": false,
        "protocol_header_present": false,
        "requested_protocol_version": "2025-03-26",
        "session_id_present": false,
        "transport": "streamable-http"
      },
      "latency_ms": 157.9,
      "status": "error"
    },
    "utility_coverage_probe": {
      "details": {
        "completions": {
          "advertised": false,
          "live_probe": "not_executed",
          "sample_target": null
        },
        "initialize_capability_keys": [],
        "pagination": {
          "metadata_signal": false,
          "next_cursor_methods": [],
          "supported": false
        },
        "tasks": {
          "advertised": false,
          "http_status": 404,
          "probe_status": "missing"
        }
      },
      "latency_ms": 158.04,
      "status": "missing"
    }
  },
  "failures": {
    "initialize": {
      "error": "Client error '404 Not Found' for url 'https://mcp-telegram.com'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
      "headers": {
        "content-type": "text/plain; charset=UTF-8"
      },
      "http_status": 404,
      "payload": {},
      "url": "https://mcp-telegram.com"
    },
    "openid_configuration": {
      "error": "Client error '404 Not Found' for url 'https://mcp-telegram.com/.well-known/openid-configuration'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
      "url": "https://mcp-telegram.com/.well-known/openid-configuration"
    },
    "server_card": {
      "error": "Client error '404 Not Found' for url 'https://mcp-telegram.com/.well-known/mcp/server-card.json'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
      "url": "https://mcp-telegram.com/.well-known/mcp/server-card.json"
    },
    "tools_list": {
      "error": "Client error '404 Not Found' for url 'https://mcp-telegram.com'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
      "headers": {
        "content-type": "text/plain; charset=UTF-8"
      },
      "http_status": 404,
      "payload": {},
      "url": "https://mcp-telegram.com"
    },
    "transport_compliance_probe": {
      "bad_protocol_error": null,
      "bad_protocol_headers": {
        "content-type": "text/plain; charset=UTF-8"
      },
      "bad_protocol_payload": {},
      "bad_protocol_status_code": 404,
      "delete_error": null,
      "delete_status_code": null,
      "expired_session_error": null,
      "expired_session_status_code": null,
      "issues": [
        "missing_protocol_header",
        "bad_protocol_not_rejected"
      ],
      "last_event_id_visible": false,
      "protocol_header_present": false,
      "requested_protocol_version": "2025-03-26",
      "session_id_present": false,
      "transport": "streamable-http"
    }
  },
  "remote_url": "https://mcp-telegram.com",
  "server_card_payload": null,
  "server_identifier": "github-overpod/mcp-telegram"
}

Known versions

Validation history

7 day score delta
n/a
30 day score delta
n/a
Recent healthy ratio
0%
Freshness
65.4h
TimestampStatusScoreLatencyTools
May 01, 2026 12:31:46 PM UTC Failing 52.8 4098.4 ms 0
May 01, 2026 12:30:02 PM UTC Failing 52.8 4076.8 ms 0
May 01, 2026 12:28:00 PM UTC Failing 52.8 4172.1 ms 0
May 01, 2026 12:23:55 PM UTC Failing 52.8 4119.1 ms 0
May 01, 2026 12:21:53 PM UTC Failing 52.8 4193.2 ms 0
May 01, 2026 12:17:42 PM UTC Failing 52.8 4083.1 ms 0
May 01, 2026 12:15:47 PM UTC Failing 52.8 4096.9 ms 0
May 01, 2026 12:13:10 PM UTC Failing 52.8 4184.4 ms 0

Validation timeline

ValidatedSummaryScoreProtocolAuth modeToolsHigh-risk toolsChanges
May 01, 2026 12:31:46 PM UTC Failing 52.8 unknown oauth_supported 0 0 none
May 01, 2026 12:30:02 PM UTC Failing 52.8 unknown oauth_supported 0 0 none
May 01, 2026 12:28:00 PM UTC Failing 52.8 unknown oauth_supported 0 0 none
May 01, 2026 12:23:55 PM UTC Failing 52.8 unknown oauth_supported 0 0 none
May 01, 2026 12:21:53 PM UTC Failing 52.8 unknown oauth_supported 0 0 none
May 01, 2026 12:17:42 PM UTC Failing 52.8 unknown oauth_supported 0 0 none
May 01, 2026 12:15:47 PM UTC Failing 52.8 unknown oauth_supported 0 0 none
May 01, 2026 12:13:10 PM UTC Failing 52.8 unknown oauth_supported 0 0 none
May 01, 2026 12:09:37 PM UTC Failing 52.8 unknown oauth_supported 0 0 none
May 01, 2026 12:06:42 PM UTC Failing 52.8 unknown oauth_supported 0 0 none
May 01, 2026 12:03:43 PM UTC Failing 52.8 unknown oauth_supported 0 0 none
May 01, 2026 12:00:08 PM UTC Failing 52.8 unknown oauth_supported 0 0 none

Recent validation runs

StartedStatusSummaryLatencyChecks
May 01, 2026 12:31:41 PM UTC Completed Failing 4098.4 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
May 01, 2026 12:29:58 PM UTC Completed Failing 4076.8 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
May 01, 2026 12:27:55 PM UTC Completed Failing 4172.1 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
May 01, 2026 12:23:51 PM UTC Completed Failing 4119.1 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
May 01, 2026 12:21:49 PM UTC Completed Failing 4193.2 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
May 01, 2026 12:17:38 PM UTC Completed Failing 4083.1 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
May 01, 2026 12:15:43 PM UTC Completed Failing 4096.9 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
May 01, 2026 12:13:06 PM UTC Completed Failing 4184.4 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
May 01, 2026 12:09:33 PM UTC Completed Failing 4035.2 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
May 01, 2026 12:06:38 PM UTC Completed Failing 4126.1 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe