← Back to search
MkTurner74/botverse-mcp

Botverse

MCP tools for video transcoding, document conversion, and multi-step pipelines — callable by any AI agent.

Decision: Allow with approval
Why: exec-capable tools + no confirmation safeguards + high-risk tools need review + unauthenticated behavior not proven
Next: export policy, require approval for writes, add authenticated validation
EXECUTIVE VERDICT

Executive verdict

Production trust decision: Allow with approval
Reason: exec-capable tools + no confirmation safeguards + high-risk tools need review + unauthenticated behavior not proven
Next action: export policy, require approval for writes, add authenticated validation
Production decision
Allow with approval
exec-capable tools + no confirmation safeguards + high-risk tools need review + unauthenticated behavior not proven
Current score
72.8
Snapshot trustsnap_15b5b198559d6788
Next action
export policy, require approval for writes, add authenticated validation
Claim the profile to add evidence, trigger validation, and configure monitoring.
Compare alternatives Export policy Open report JSON
Observed Attention
No observed attention
No observed attention in the current 30-day window.
  • No segmented attention signals observed in the current window.
Bucketed signal based on recent segmented Verify telemetry. Crawler and evaluator activity is not treated as confirmed human demand.
Status
Healthy
Score
72.8
Transport
streamable-http
Tools
15

Current trust snapshot

Snapshot ID
trustsnap_15b5b198559d6788
Use this ID to compare server page, report, policy, MCP, homepage, ranking, and shortlist surfaces.
Snapshot generated
Jul 31, 2026 12:01:23 PM UTC
All page, report, policy, and MCP surfaces use this same server-detail snapshot shape.
Last validated
Jul 31, 2026 10:25:44 AM UTC
Age: 1.59h • freshness band: Verified in last 24h • display score: 72.76
Production trust decision
Allow with approval
exec-capable tools + no confirmation safeguards + high-risk tools need review + unauthenticated behavior not proven
Readiness class
Safe for evaluation
The server is suitable for evaluation, but remaining gaps should be resolved before broad production use.

Canonical machine links

SERVER OWNER FUNNEL

Own this MCP?

Claim ownership, prove control with a GitHub, DNS, HTTP, MCP metadata, or email-domain challenge, revalidate now, publish a badge, configure monitoring, and unlock a verified server profile.

1. Claim
unclaimed
with GitHub, DNS, or HTTP challenge instructions.
2. Revalidate
POST /v1/servers/MkTurner74/botverse-mcp/revalidate
Verified owners get priority queueing after proof succeeds.
3. Badge
Verified by MCP Verify badge
Verified by MCP Verify - score 72.8 - last checked Jul 31, 2026
4. Monitor
Continuous Verify plan is self-serve: choose a tier, configure watches, add authenticated validation, trigger revalidation, and use the badge.
Paid profile
Add verified publisher identity, security metadata, evidence packs, badge customization, and owner analytics without buying a better score.
Badge embed
[![Verified by MCP Verify](https://verify.sentinelsignal.io/badge/MkTurner74/botverse-mcp.svg)](https://verify.sentinelsignal.io/servers/MkTurner74/botverse-mcp)

MCP TrustOps

TrustOps turns this report into operational controls: freshness SLAs, authenticated validation, semantic benchmarks, policy exports, alert subscriptions, badges, cost/compliance metadata, and runtime routing. Fresh trusted index decisions stay separate from long-tail inventory so stale scores do not masquerade as current evidence.

Freshness band
Verified in last 24h
Policy SLA: 168.0h • confidence-weighted score: 55.5 • stale score suppressed:
Policy exports
Formats: json, rego, yaml, github_action, gateway_config, client_report
Runtime routing
/v1/decide
Returns allowed tools, blocked tools, approval requirement, and reason.
Hosted runtime
Deploy trusted servers from GitHub with secrets, egress controls, releases, rollback, and audit events.
Authenticated validation
Premium publisher feature: paid authenticated runs verify scopes, write-action safeguards, and authorized tool execution.
Active trust badges
Freshly Validated OAuth Verified OpenAI App Compatible Claude Remote MCP Compatible No Critical Risk
Semantic benchmarks
available
Templates cover GitHub, database, healthcare, web search, and CRM least-privilege jobs.
Supply chain
metadata signal
Deep scan checks are marked separately from public metadata signals.
Compliance metadata
Terms, privacy, SOC 2, HIPAA, GDPR, retention, deletion, and audit-log fields are tracked as enterprise metadata.
Alert subscription types
Status changes Score drops or recovers Freshness SLA breach Validation schema drift OAuth or auth behavior changes Tool surface changes New or changed write tool Supply-chain signal changes Legal or compliance metadata changes

MCP Runtime hosting

Verify Hosted MCP turns a trusted server report into a managed remote MCP endpoint with GitHub deployment provenance, sandbox policy, encrypted secrets, release history, rollback, and audit/usage events.

Activation readiness
Trusted hosted runtimes require fresh validation, a passing server state, a remote endpoint, and a minimum score.
Minimum tier
TrustOps
Publisher claim plus paid TrustOps tier are required before secrets or releases can be created.
Hosted endpoint
/hosted/{namespace}/{name}/mcp
The endpoint enforces egress allowlists and records audit/usage events.
Blockers
none
DeploymentStatusEndpointRelease
No hosted runtime deployments yet.

Production readiness class

Production readiness class
Safe for evaluation
The server is suitable for evaluation, but remaining gaps should be resolved before broad production use.
Critical alerts
0
Production verdicts degrade quickly when critical alerts are active.

Evidence confidence

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

Recommended for

OpenAI connectors
OpenAI connectors is marked compatible with score 89.
Claude Desktop
Claude Desktop is marked compatible with score 83.
Smithery
Smithery is marked compatible with score 80.
Generic Streamable HTTP
Generic Streamable HTTP is marked compatible with score 100.

Client compatibility verdicts

Client compatibility only means the server shape can work with a client. Production trust decision and write-action publishing are evaluated separately so a client-compatible server can still be blocked for production.

Client compatibility: ChatGPT
Client-compatible
Transport compliance should be in good shape.
Confidence: high (76.25)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initializeOK
  • tools_listOK
  • transport_compliance_probeError
  • step_up_auth_probeOK
  • connector_replay_probeMissing — Frozen tool snapshots must survive refresh.
  • request_association_probeMissing — Roots, sampling, and elicitation should stay request-scoped.
Client compatibility: Claude
Client-compatible
Transport behavior should match Claude-compatible HTTP expectations.
Confidence: high (76.25)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initializeOK
  • tools_listOK
  • transport_compliance_probeError
Write-action publishing
Publishing allowed
Current write surface is bounded enough for cautious review with production policy controls.
Confidence: high (76.25)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history
Disagreements: none
  • action_safety_probeWarning
Snapshot churn risk
Low
No material tool-surface churn detected in the latest comparison.
Confidence: high (76.25)
Evidence provenance
Winner: history
Supporting sources: history, live_validation
Disagreements: none
  • tool_snapshot_probeMissing
  • connector_replay_probeMissing

Why compatibility is limited by client

ChatGPT custom connector
Client-compatible
Remediation checklist
  • Transport compliance should be in good shape.
  • search fetch only is not yet satisfied
  • admin refresh required is not yet satisfied
  • safe for company knowledge is not yet satisfied
  • safe for messages api remote mcp is not yet satisfied
  • Transport compliance issues should be resolved before wider client rollout.
Claude remote MCP
Client-compatible
Remediation checklist
  • Transport behavior should match Claude-compatible HTTP expectations.
  • search fetch only is not yet satisfied
  • admin refresh required is not yet satisfied
  • safe for company knowledge is not yet satisfied
  • safe for messages api remote mcp is not yet satisfied
  • Transport compliance issues should be resolved before wider client rollout.
Write-safe publishing
Ready
Remediation checklist
  • No explicit blockers recorded.

Verdict traces

Production verdict
Safe for evaluation
The server is suitable for evaluation, but remaining gaps should be resolved before broad production use.
Confidence: high (76.25)
Winning source: live_validation
Triggering alerts
  • No active alert triggers.
Client verdict trace table
VerdictStatusChecksWinning sourceConflicts
openai_connectors Client-compatible initialize, tools_list, transport_compliance_probe, step_up_auth_probe, connector_replay_probe, request_association_probe live_validation none
claude_desktop Client-compatible initialize, tools_list, transport_compliance_probe live_validation none
unsafe_for_write_actions Publishing allowed action_safety_probe live_validation none
snapshot_churn_risk Low tool_snapshot_probe, connector_replay_probe history none

Publishability policy profiles

ChatGPT custom connector compatibility
Connector-compatible
Transport compliance should be in good shape. Compatibility is not a production approval; company knowledge and Messages API gates remain separate.
  • Search Fetch Only: No
  • Write Actions Present: Yes
  • Oauth Configured: Yes
  • Admin Refresh Required: No
  • Safe For Company Knowledge: No
  • Safe For Messages Api Remote Mcp: No
Claude remote MCP compatibility
Connector-compatible
Transport behavior should match Claude-compatible HTTP expectations. Compatibility is not a production approval; company knowledge and Messages API gates remain separate.
  • Search Fetch Only: No
  • Write Actions Present: Yes
  • 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
Passes
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
Transport behavior should match Claude-compatible HTTP expectations.
  • remote_transport: Passes
  • tool_discovery: Passes
  • auth_connect: Passes
  • safe_write_review: Passes

Authenticated validation sessions

Public validation is free. Authenticated validation is paid and proves scoped behavior, write-action safeguards, and authenticated tool execution.

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
1.0
Validation success 30d
1.0
Mean time to recover
n/a
Breaking diffs 30d
0
Registry drift frequency 30d
0
Snapshot changes 30d
0

Incident & change feed

TimestampEventDetails
Jul 31, 2026 10:25:44 AM UTC Latest validation: healthy Score 72.8 with status healthy.

Capabilities

Use-case taxonomy
development communication productivity web

Security posture

Tools analyzed
15
High-risk tools
8
Destructive tools
3
Exec tools
8
Egress tools
6
Secret tools
4
Bulk-access tools
7
Risk distribution
low:1, medium:6, high:3, critical:5

Agent Commerce & Payment Readiness - Beta

Beta assessment. Verify separates commerce-adjacent context from observed payment execution. Usage, billing, pricing, card, wallet, or meter terms alone do not make a server payment-capable. This is not a certification of safety, compliance, or fraud prevention.

Overall
74
Auth posture
90
Payment readiness
75
Delegation safety
70
Tool risk
70
Commerce signal: moderate Payment capable: inferred Payment execution: no Billing/usage context: yes Quote/pricing context: yes Numeric price context: yes Commercial quote context: yes Checkout/charge signal: no Checkout term observed: no Human confirmation: yes Spending policy: yes Receipt support: unknown Auth required: yes Operator identity: declared Tool risk: administrative Delegation level: usage metering context
Detected payment rails
none detected
Purchase stages
usage_metering
Evidence level
inferred
Confidence
medium

Warnings

Evidence

FieldValueSourceMatched termsConfidence
commerce_signalmoderatetool_schemaorder, billing, limit, amount, balance, rate, walletmedium

Recommended operator fixes

Tool capability & risk inventory

ToolCapabilitiesRiskFindingsNotes
get_upload_url read write network filesystem Medium freeform input surface filesystem mutation Safeguards hinted in metadata.
transcode_from_url read write delete exec network filesystem admin secrets export Critical destructive operation command execution arbitrary network egress bulk data access secret material access freeform input surface filesystem mutation admin mutation Safeguards hinted in metadata.
transcode_video read write exec network filesystem admin secrets export Critical command execution arbitrary network egress bulk data access secret material access freeform input surface filesystem mutation admin mutation Safeguards hinted in metadata.
get_job_status read network filesystem Medium none No explicit safeguard hints detected.
get_download_url read write network filesystem Medium arbitrary network egress filesystem mutation Safeguards hinted in metadata.
get_output_content read write network filesystem Medium filesystem mutation Safeguards hinted in metadata.
get_wallet_balance read Low none Safeguards hinted in metadata.
convert_from_url read write delete exec network filesystem export Critical destructive operation command execution arbitrary network egress bulk data access freeform input surface filesystem mutation Safeguards hinted in metadata.
convert_file read write exec network filesystem export High command execution bulk data access freeform input surface filesystem mutation Safeguards hinted in metadata.
submit_workflow read write exec network admin High command execution admin mutation No explicit safeguard hints detected.
get_workflow_status read write Medium none No explicit safeguard hints detected.
cancel_workflow write Medium none No explicit safeguard hints detected.
convert_content read write exec network filesystem export High command execution bulk data access filesystem mutation Safeguards hinted in metadata.
transcribe_from_url read write delete exec network filesystem admin secrets export Critical destructive operation command execution arbitrary network egress bulk data access secret material access freeform input surface filesystem mutation admin mutation Safeguards hinted in metadata.
transcribe_media read write exec network filesystem admin secrets export Critical command execution arbitrary network egress bulk data access secret material access freeform input surface filesystem mutation admin mutation Safeguards hinted in metadata.

Write-action governance

Governance status
Warning
Safe to publish
Auth boundary
oauth_or_auth_required
Blast radius
High
High-risk tools
8
Confirmation signals
get_wallet_balance
Safeguard count
11

Status detail: 8 high-risk tool(s), 3 destructive tool(s), 8 exec-capable tool(s); auth boundary is oauth or auth required with 11 safeguard(s) and 1 confirmation signal(s).

ToolRiskFlagsSafeguards
transcode_from_url Critical destructive operation command execution arbitrary network egress bulk data access secret material access freeform input surface filesystem mutation admin mutation yes
transcode_video Critical command execution arbitrary network egress bulk data access secret material access freeform input surface filesystem mutation admin mutation yes
convert_from_url Critical destructive operation command execution arbitrary network egress bulk data access freeform input surface filesystem mutation yes
convert_file High command execution bulk data access freeform input surface filesystem mutation yes
submit_workflow High command execution admin mutation no
convert_content High command execution bulk data access filesystem mutation yes
transcribe_from_url Critical destructive operation command execution arbitrary network egress bulk data access secret material access freeform input surface filesystem mutation admin mutation yes
transcribe_media Critical command execution arbitrary network egress bulk data access secret material access freeform input surface filesystem mutation admin mutation yes

Action-controls diff

Snapshot changed
no
Disabled-by-default candidates
none
Manual review candidates
none
New actions
ActionRiskFlags
No newly added actions.
Changed actions
ActionChange typesRisk
No materially changed actions.

Why this score?

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

Algorithmic score breakdown

Auth Operability
4/4
Measures whether auth discovery and protected access behave predictably for clients.
Error Contract Quality
0/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
3/4
Completeness of tool descriptions, parameter docs, examples, and schema shape.
Backward Compatibility
2/4
Stability score across tool schema/name drift relative to prior validations.
SLO Health
4/4
Availability, latency, and burst-failure profile across recent validation history.
Security Hygiene
4/4
HTTPS posture, endpoint hygiene, and response-surface hardening checks.
Task Success
4/4
Can an agent reliably initialize, enumerate tools, and execute core MCP flows?
Trust Confidence
1.8/4
Confidence-adjusted reliability score that penalizes low evidence volume.
Abuse/Noise Resilience
4/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.6/4
Agreement between stored registry metadata, live server-card data, and current validation output.
Installability
4/4
How cleanly a real client can connect, initialize, enumerate tools, and proceed through auth.
Session Semantics
4/4
Determinism and state behavior across repeated MCP calls, including sticky-session surprises.
Tool Surface Design
4/4
Naming clarity, schema ergonomics, and parameter complexity across the tool surface.
Result Shape Stability
3/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/4
Whether failures include actionable machine-readable next steps such as retry or upgrade guidance.
Maintenance Signal
4/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
4/4
Whether declared transport metadata matches the observed endpoint behavior and response formats.
Spec Recency
4/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
3/4
Coverage of newer MCP surfaces like roots, sampling, elicitation, structured output, and related metadata.
Connector Publishability
3/4
How ready the server looks for client catalogs and managed connector programs.
Tool Snapshot Churn
3/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
4/4
Whether prompts and docs steer users toward safe auth flows instead of pasting secrets directly.
Action Safety
2/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
4/4
How clearly the tool surface communicates whether each action reads, writes, deletes, executes, or exports data.
Destructive Operation Safety
3.8/4
Penalizes delete/revoke/destroy style tools unless auth and safeguards reduce blast radius.
Egress / SSRF Resilience
3.5/4
Assesses arbitrary URL fetch, crawl, webhook, and remote-request exposure on the tool surface.
Execution / Sandbox Safety
1.5/4
Evaluates shell, code, script, and command-execution exposure and whether that surface appears contained.
Data Exfiltration Resilience
2/4
Assesses export, dump, backup, and bulk-read behavior against the surrounding auth and safeguard signals.
Least Privilege Scope
2/4
Rewards scoped auth metadata and penalizes broad or missing scopes around privileged tools.
Secret Handling Hygiene
4/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
3/4
Penalizes risky freeform string inputs when schemas do not constrain URLs, code, paths, queries, or templates.
Tool Namespace Clarity
4/4
Measures naming uniqueness and ambiguity across the tool namespace to reduce collision and confusion risk.

Compatibility profiles

OpenAI Connectors
88.9
compatible
Transport compliance should be in good shape.
Connector URL: https://botverse.cloud/mcp?token=bv_sess_
# Complete OAuth in the client when prompted.
# Server: MkTurner74/botverse-mcp
Claude Desktop
83.3
compatible
Transport behavior should match Claude-compatible HTTP expectations.
{
  "mcpServers": {
    "botverse-mcp": {
      "command": "npx",
      "args": ["mcp-remote", "https://botverse.cloud/mcp?token=bv_sess_"]
    }
  }
}
Smithery
80.0
compatible
Machine-readable failure semantics should be present.
smithery mcp add "https://botverse.cloud/mcp?token=bv_sess_"
Generic Streamable HTTP
100.0
compatible
No major blockers detected.
curl -sS https://botverse.cloud/mcp?token=bv_sess_ -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
High Add confirmation and dry-run semantics for risky actions High-risk write, delete, exec, or egress tools should communicate safeguards clearly. 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 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 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 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
Recovery Semantics 0/4 -4.0
Error Contract 0/4 -4.0
Dependency Supply Chain Signal 0.5/4 -3.5
Execution Sandbox Safety 1.5/4 -2.5
Trust Confidence 1.8/4 -2.2
Utility Coverage 2/4 -2.0
Safety Transparency 2/4 -2.0
Resource Contract 2/4 -2.0
Rate Limit Semantics 2/4 -2.0
Prompt Contract 2/4 -2.0
Least Privilege Scope 2/4 -2.0

Validation diff

Need at least two validation runs before diffing changes.

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
200
DELETE teardown
n/a
Expired session retry
n/a
Last-Event-ID visible
no

Issues: missing_session_id, 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 Passes
  • initializeOK
  • tools_listOK
Read-only fetch flow Degraded
  • resource_readMissing
  • read_only_tool_surfaceOK
OAuth-required connect Passes
  • oauth_protected_resourceOK
  • step_up_auth_probeOK
Safe write flow with confirmation Degraded
  • action_safety_probeWarning

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

No active alerts for the current server state.

Aliases & registry graph

IdentifierSourceCanonicalScore
MkTurner74/botverse-mcp glama_registry yes 72.76
awesome-mkturner74/botverse-mcp awesome_mcp_servers no 44.39

Alias consolidation

Source disagreements
FieldWhat differsObserved values
Registry source Multiple registries or registry sync paths claim this same canonical server. awesome_mcp_servers glama_registry
Remote URL Aliases currently point at different MCP endpoints, which can indicate mirrors, stale registry data, or a real endpoint split. https://botverse.cloud/mcp?token=bv_sess_ https://glama.ai/mcp/servers/MkTurner74/botverse-mcp/badges/score.svg)](https://glama.ai/mcp/servers/MkTurner74/botverse-mcp
Homepage Registry entries disagree on the primary homepage for this server. https://github.com/MkTurner74/botverse-mcp https://glama.ai/mcp/servers/j4rjqjpbd0
Registry identifier Different registry-specific identifiers resolve to the same canonical server record here. awesome_mcp_servers:MkTurner74/botverse-mcp glama_registry:j4rjqjpbd0

Install snippets

Openai Connectors
Connector URL: https://botverse.cloud/mcp?token=bv_sess_
# Complete OAuth in the client when prompted.
# Server: MkTurner74/botverse-mcp
Claude Desktop
{
  "mcpServers": {
    "botverse-mcp": {
      "command": "npx",
      "args": ["mcp-remote", "https://botverse.cloud/mcp?token=bv_sess_"]
    }
  }
}
Smithery
smithery mcp add "https://botverse.cloud/mcp?token=bv_sess_"
Generic Http
curl -sS https://botverse.cloud/mcp?token=bv_sess_ -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
get_upload_url transcode_from_url transcode_video get_job_status get_download_url get_output_content get_wallet_balance convert_from_url
Observed from the latest live validation against https://botverse.cloud/mcp?token=bv_sess_. This is the target server surface, not Verify's own inspection tools.
Live capability counts
15 tools • 0 prompts • 0 resources
Counts come from the latest tools/list, prompts/list, and resources/list checks.
Inspect with Verify
search fetch search_servers recommend_servers get_server_report compare_servers
Use Verify itself to search, recommend, compare, and fetch the full report for MkTurner74/botverse-mcp.
Direct machine links

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
1
Average Latency Ms
1143.12
Healthy Run Ratio Recent
1.0
Registry Presence Count
2
Active Alert Count
0
Watcher Count
0
Verified Claim
False
Taxonomy Tags
development, communication, productivity, web
Score Trend
72.76
Remediation Count
13
High Risk Tool Count
8
Destructive Tool Count
3
Exec Tool Count
8

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
Healthy
Validation profile
remote_mcp
Started
Jul 31, 2026 10:25:43 AM UTC
Latency
1143.1 ms

Failures

Checks

CheckStatusLatencyEvidence
action_safety_probe Warning n/a 8 high-risk, 3 destructive, 8 exec-capable tool(s); auth present; safeguards=11; confirmation=get wallet balance.
advanced_capabilities_probe Warning n/a Only 3 capability signal(s): prompts, resources, structured outputs.
connector_publishability_probe Warning n/a Publishability blockers: transport compliance, server card.
connector_replay_probe Missing n/a No connector replay evidence recorded.
determinism_probe OK 37.3 ms Check completed
initialize OK 74.3 ms Protocol 2024-11-05
interactive_flow_probe OK n/a Check completed
oauth_authorization_server OK 54.9 ms authorization_endpoint, code_challenge_methods_supported, grant_types_supported, issuer
oauth_protected_resource OK 113.7 ms 1 authorization server(s)
official_registry_probe Warning n/a Check completed
openid_configuration Error 27.4 ms Client error '404 Not Found' for url 'https://botverse.cloud/.well-known/openid-configuration' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
probe_noise_resilience OK 16.0 ms Fetched https://botverse.cloud/robots.txt
prompt_get Missing n/a not advertised
prompts_list OK 95.1 ms 0 prompt(s) exposed
protocol_version_probe Warning n/a Claims 2024-11-05; 3 release(s) behind 2025-11-25.
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 OK 41.8 ms 0 resource item(s) exposed
server_card Error 84.5 ms Client error '404 Not Found' for url 'https://botverse.cloud/.well-known/mcp/server-card.json' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
session_resume_probe Warning n/a no session id
step_up_auth_probe OK n/a Scopes=botverse:jobs, botverse:read, botverse:wallet.
tool_snapshot_probe Missing n/a no historical snapshot
tools_list OK 43.3 ms 15 tool(s) exposed
transport_compliance_probe Error 36.3 ms Issues: missing session id, missing protocol header, bad protocol not rejected (bad protocol=200).
utility_coverage_probe Missing 468.2 ms No completions evidence; no pagination evidence; tasks missing.

Raw evidence view

Show raw JSON evidence

Large evidence payload summarized to keep this page fast. Full raw evidence remains available from the JSON report.

{
  "checks": {
    "count": 26,
    "items": {
      "action_safety_probe": {
        "auth_present": true,
        "safeguard_count": 11,
        "status": "warning"
      },
      "advanced_capabilities_probe": {
        "status": "warning"
      },
      "connector_publishability_probe": {
        "status": "warning"
      },
      "connector_replay_probe": {
        "reason": "no_historical_snapshot",
        "status": "missing"
      },
      "determinism_probe": {
        "latency_ms": 37.3,
        "status": "ok"
      },
      "initialize": {
        "http_status": 200,
        "latency_ms": 74.34,
        "payload_omitted": true,
        "status": "ok"
      },
      "interactive_flow_probe": {
        "status": "ok"
      },
      "oauth_authorization_server": {
        "http_status": 200,
        "latency_ms": 54.91,
        "payload_omitted": true,
        "status": "ok"
      },
      "oauth_protected_resource": {
        "http_status": 200,
        "latency_ms": 113.67,
        "payload_omitted": true,
        "status": "ok"
      },
      "official_registry_probe": {
        "status": "warning"
      },
      "openid_configuration": {
        "latency_ms": 27.41,
        "reason": "Client error '404 Not Found' for url 'https://botverse.cloud/.well-known/openid-configuration'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "status": "error"
      },
      "probe_noise_resilience": {
        "http_status": 200,
        "latency_ms": 16.0,
        "status": "ok"
      },
      "prompt_get": {
        "reason": "not_advertised",
        "status": "missing"
      },
      "prompts_list": {
        "http_status": 200,
        "latency_ms": 95.06,
        "payload_omitted": true,
        "status": "ok"
      },
      "protocol_version_probe": {
        "status": "warning"
      },
      "provenance_divergence_probe": {
        "status": "ok"
      },
      "request_association_probe": {
        "reason": "no_request_association_capabilities_advertised",
        "status": "missing"
      },
      "resource_read": {
        "reason": "not_advertised",
        "status": "missing"
      },
      "resources_list": {
        "http_status": 200,
        "latency_ms": 41.83,
        "payload_omitted": true,
        "status": "ok"
      },
      "server_card": {
        "latency_ms": 84.45,
        "reason": "Client error '404 Not Found' for url 'https://botverse.cloud/.well-known/mcp/server-card.json'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "status": "error"
      },
      "session_resume_probe": {
        "reason": "no_session_id",
        "status": "warning"
      },
      "step_up_auth_probe": {
        "status": "ok"
      },
      "tool_snapshot_probe": {
        "reason": "no_historical_snapshot",
        "status": "missing"
      },
      "tools_list": {
        "http_status": 200,
        "latency_ms": 43.3,
        "payload_omitted": true,
        "status": "ok",
        "tool_count": 15,
        "tool_names_preview": [
          "get_upload_url",
          "transcode_from_url",
          "transcode_video",
          "get_job_status",
          "get_download_url",
          "get_output_content",
          "get_wallet_balance",
          "convert_from_url",
          "convert_file",
          "submit_workflow",
          "get_workflow_status",
          "cancel_workflow",
          "convert_content",
          "transcribe_from_url",
          "transcribe_media"
        ]
      },
      "transport_compliance_probe": {
        "latency_ms": 36.26,
        "protocol_header_present": false,
        "status": "error"
      },
      "utility_coverage_probe": {
        "latency_ms": 468.25,
        "status": "missing"
      }
    },
    "omitted_count": 0
  },
  "failures": {
    "count": 3,
    "items": {
      "openid_configuration": {},
      "server_card": {},
      "transport_compliance_probe": {}
    },
    "omitted_count": 0
  },
  "message": "Raw evidence is summarized in HTML to keep server detail pages fast. Use the JSON report or evidence API for the full payload.",
  "remote_url": "https://botverse.cloud/mcp?token=bv_sess_",
  "server_card": {
    "name": null,
    "raw_payload_omitted": false,
    "version": null
  },
  "server_identifier": "MkTurner74/botverse-mcp",
  "truncated": true
}

Known versions

Validation history

7 day score delta
n/a
30 day score delta
n/a
Recent healthy ratio
100%
Freshness
1.6h
TimestampStatusScoreLatencyTools
Jul 31, 2026 10:25:44 AM UTC Healthy 72.8 1143.1 ms 15

Validation timeline

ValidatedSummaryScoreProtocolAuth modeToolsHigh-risk toolsChanges
Jul 31, 2026 10:25:44 AM UTC Healthy 72.8 2024-11-05 oauth_supported 15 8 none

Recent validation runs

StartedStatusSummaryLatencyChecks
Jul 31, 2026 10:25:43 AM UTC Completed Healthy 1143.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