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

Vibes-Coded Agent Security and Commerce Tools

REMOTE · VIBES-CODED-MCP-PRODUCTION.UP.RAILWAY.APP · SCANNED OCT 12

Agent supply-chain security, scanner consensus, x402 reliability, and commerce MCP tools.

0 this week 84 Trust /100
Trust breakdown (7 categories)

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

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 4687 tokens (~142/item across 33 items; 33 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety83
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 1 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "vc_lease_revoke" implies "revoke" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
  • An AI judge read all 34 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Vibes-Coded Agent Security and Commerce Tools MCP server?

Vibes-Coded Agent Security and Commerce Tools is a hosted endpoint at https://vibes-coded-mcp-production.up.railway.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · vibes-coded-mcp-production.up.railway.app

# add to Claude Code
claude mcp add --transport http doteyeso-ops-mcp-server-vibes-coded 'https://vibes-coded-mcp-production.up.railway.app/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "doteyeso-ops-mcp-server-vibes-coded": {
      "url": "https://vibes-coded-mcp-production.up.railway.app/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "doteyeso-ops-mcp-server-vibes-coded": {
      "type": "http",
      "url": "https://vibes-coded-mcp-production.up.railway.app/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.doteyeso-ops-mcp-server-vibes-coded]
url = "https://vibes-coded-mcp-production.up.railway.app/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "doteyeso-ops-mcp-server-vibes-coded": {
      "type": "remote",
      "url": "https://vibes-coded-mcp-production.up.railway.app/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add doteyeso-ops-mcp-server-vibes-coded --url 'https://vibes-coded-mcp-production.up.railway.app/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  doteyeso-ops-mcp-server-vibes-coded:
    url: "https://vibes-coded-mcp-production.up.railway.app/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "doteyeso-ops-mcp-server-vibes-coded": {
      "Transport": "http",
      "Url": "https://vibes-coded-mcp-production.up.railway.app/mcp"
    }
  }
}
# add to Vellum
assistant mcp add doteyeso-ops-mcp-server-vibes-coded -t streamable-http -u 'https://vibes-coded-mcp-production.up.railway.app/mcp'
// mcp.json
{
  "mcpServers": {
    "doteyeso-ops-mcp-server-vibes-coded": {
      "type": "http",
      "url": "https://vibes-coded-mcp-production.up.railway.app/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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

  • 30 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 3461 → 4687 ▼ functional
    • Destructive annotations: 50% → 33% ▼ functional
    • Server version: 1.29.1 → 1.30.0 functional
    • New tool “vc_marketplace_search” functional
    • New tool “vc_marketplace_details” functional
    • New tool “vc_lease_status” functional
    • New tool “vc_lease_revoke” functional
    • New tool “vc_lease_issue” functional
    • New tool “vc_lease_consume” functional
    • New tool “vc_agent_proof” functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 0
    • Stability: 0.97 → pass security
  • 23 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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

Captured 12 Oct 2026 · Probed https://vibes-coded-mcp-production.up.railway.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.up.railway.app CN=YE2,O=Let's Encrypt,C=US 27 Sept 2026 26 Dec 2026 ECDSA 256 ECDSA-SHA384 618edc56941aa1165ddb080bf9f799eb7c1
SANs: *.up.railway.app, up.railway.app
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of vibes-coded-mcp-production.up.railway.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
railway.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

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

Result No authorisation required
HTTP status 200

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://vibes-coded-mcp-production.up.railway.app/mcp Verified 200
http (plaintext) http://vibes-coded-mcp-production.up.railway.app/mcp HTTPS enforced 301 https://vibes-coded-mcp-production.up.railway.app/mcp
MCP tools · 33 exposed · ~4,621 tokens

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

Tool Tokens
health ~90

Return MCP server liveness: version, origin, tool count, and catalog size. Use for hosted inspector probes (Glama / Smithery) or before diagnosing tool failures. Do not use for business outcomes — call vc_* tools or pay(slug=...) instead. No auth required. No side effects. Returns JSON {ok, service, version, origin, tools, catalog_resources}.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

pay ~250

Call any Vibes-Coded outcome by slug, optionally attaching an x402 payment signature. Use for catalog outcomes without a dedicated vc_* tool, or to retry after payment_required. Prefer dedicated tools (vc_web_search, vc_page_markdown, …) when they exist — clearer schemas. Do not use instead of health(). Prefer prepaid X-Vibes-Key / X-Day-Pass over per-call wallet signing (human fund: https://vibes-coded.com/start). Args: slug: Outcome id, e.g. "web-search" or "agent-state-guard". payment_signature: Optional x402 PAYMENT-SIGNATURE header value. body: JSON object of endpoint fields (query, url, text, …). Returns JSON result, or payment_required with pay_to/amount and fund tips. Side effects: may settle USDC via x402 when paying; otherwise HTTP only.

NameTypeReqDescription
body––JSON object of endpoint fields (query, url, text, …).
payment_signature––Optional x402 PAYMENT-SIGNATURE header value.
slugstringyesOutcome id, e.g. web-search or agent-state-guard.
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_agent_proof ~192

Verify an agent's completion claim against real external world state. Runs independent read-back checks (HTTP status, page text, JSON fields) and returns a digest receipt with verified=true/false plus a confidence score, so a user does not have to trust the agent's self-reported summary. Use after an agent says it posted, deployed, paid, emailed or changed a record. ~$0.25/call.

NameTypeReqDescription
agent_id––Stable id for the agent being verified.
checks_jsonstring–JSON array of read-back checks, e.g. [{"name":"homepage live","url":"https://example.com/","expected_status":200,"contains":"Example"}]
claimstringyesWhat the agent claims it did (its final report).
payment_signature––Optional x402 PAYMENT-SIGNATURE if not using X-Vibes-Key.
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_agent_reputation ~121

Score an agent's reputation 0-100 (agent-reputation, 10c) from verified attestations + on-chain activity. Check an agent before you pay it. Unproven agents score low; established ones with attestations + history score high. Sibling: vc_attest, vc_attest_verify, vc_agent_leaderboard.

NameTypeReqDescription
agent_idstringyesAgent id to score (0-100).
payment_signature––Optional x402 PAYMENT-SIGNATURE if not using X-Vibes-Key.
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_agent_state_guard ~188

Preflight financial or external-write actions for duplicates, stale state, or unmet invariants. Use before spending money or writing outside the agent sandbox. Do not use for generic search — use vc_web_search. Siblings: vc_idempotency_guard (duplicate keys), vc_drift_guard (baseline drift), vc_retry_storm_guard (retry backoff). Auth: X-Vibes-Key or x402 (~$0.02). Advisory only; no local writes. Returns GO/NO-GO style JSON with reasons, or payment_required.

NameTypeReqDescription
actionstringyesProposed action label (e.g. transfer, write_external, publish).
invariants––Optional invariant strings that must still hold.
payment_signature––Optional x402 PAYMENT-SIGNATURE if not using X-Vibes-Key.
state––Current agent/business state snapshot.
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_attest ~154

Sign a claim offline-verifiable (attest, 5c). Returns a signed attestation (Ed25519 + HMAC receipt). Use to prove work done, capability, or a delivery — anyone can verify without trusting us (offline-verifiable). Sibling: vc_attest_verify, vc_agent_reputation.

NameTypeReqDescription
agent_idstring–Agent making/attesting the claim.
claim_typestringyeswork_done | identity | capability | observation | delivery | receipt | permission
payment_signature––Optional x402 PAYMENT-SIGNATURE if not using X-Vibes-Key.
statementstringyesThe claim itself.
subjectstring–Claim subject.
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_attest_verify ~76

Verify a signed attestation offline (attest-verify, 2c). Tampered claims fail. Sibling: vc_attest.

NameTypeReqDescription
claimobjectyesThe attestation object returned by vc_attest.
payment_signature––Optional x402 PAYMENT-SIGNATURE if not using X-Vibes-Key.
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_drift_guard ~156

Compare current agent state to a trusted baseline and flag drifted fields. Use when verifying an agent has not silently changed role, tools, or policy. Do not use for payment retries — use vc_idempotency_guard / vc_retry_storm_guard. Auth: X-Vibes-Key or x402 (~$0.02). Advisory only. Returns JSON listing drifted fields and severity, or payment_required.

NameTypeReqDescription
baselineobjectyesTrusted baseline or prior trajectory.
currentobjectyesCurrent agent state or config object.
fields––Optional field paths to watch; omit to compare broadly.
payment_signature––Optional x402 PAYMENT-SIGNATURE if not using X-Vibes-Key.
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_idempotency_guard ~186

Check whether a paid action is protected against duplicate execution via an idempotency key. Use before retrying a payment or other side-effecting call. Do not use for content fetch — use vc_web_search / vc_page_markdown. Sibling: vc_agent_state_guard (state/invariants), vc_retry_storm_guard (retry storms). Auth: X-Vibes-Key or x402 (~$0.02). Advisory only; no local writes. Returns JSON assessing key presence/durability, or payment_required.

NameTypeReqDescription
action––Action being protected.
durable_store––Where keys are stored (redis, db, etc.), if known.
idempotency_keystringyesClient key that should uniquely protect this paid action.
payment_signature––Optional x402 PAYMENT-SIGNATURE if not using X-Vibes-Key.
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_json_repair ~151

Repair malformed JSON from LLM output and return valid parsed JSON. Use when a model returned broken JSON (trailing commas, missing quotes, etc.). Do not use for web fetching or search — use vc_web_search / vc_page_markdown. Auth: free-trial or X-Vibes-Key preferred; else x402 (~$0.02). Side effects: none local; compute-only remote call. Idempotent for the same text. Returns repaired JSON, or payment_required.

NameTypeReqDescription
payment_signature––Optional x402 PAYMENT-SIGNATURE if not using X-Vibes-Key.
textstringyesMalformed JSON or JSON-like text from an LLM.
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_lease_consume ~203

Spend exactly one use of a lease, atomically. Blocks replay, expiry, revocation and overuse. Returns decision allow/block with a named reason plus an Ed25519 decision receipt. If a previous attempt timed out, call this again with the SAME use_nonce: a replay returns reason=replay — do not retry the write, reconcile it. ~$0.02/call.

NameTypeReqDescription
action––What you are about to do, for the ledger trail.
agent_id––Caller identity; must match the lease holder unless it was issued to '*'.
lease_id––Lease to spend from.
lease_token––Signed lease token from vc_lease_issue (alternative to lease_id).
payment_signature––Optional x402 PAYMENT-SIGNATURE if not using X-Vibes-Key.
use_noncestringyesStable id for this attempt (the replay key). Reuse the SAME nonce on retry.
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_lease_issue ~237

Mint a durable single-use capability lease, or attenuate a parent lease. Use before an irreversible action you may need to retry: pass a stable use_nonce to vc_lease_consume so a retry after a timeout blocks instead of writing twice. Authority is conserved — a child's uses are reserved out of the parent, so a 1-use grant cannot father N free children. ~$0.05/call.

NameTypeReqDescription
action_scopestringyesSpace-separated scope atoms the lease grants, e.g. 'read:repo write:issue'.
holderstringyesAgent the authority belongs to. Use '*' for any holder.
max_usesinteger–How many times this authority may be spent (1..10000).
parent_lease_id––Attenuate from this parent: child scope must be a subset, and its uses are transferred out of the parent.
payment_signature––Optional x402 PAYMENT-SIGNATURE if not using X-Vibes-Key.
ttl_secondsinteger–Seconds until expiry. Secondary check only: the ledger is the authority.
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_lease_revoke ~113

Revoke a lease and (by default) its whole subtree so derived authority dies with its source. Use when an agent is misbehaving or a task is cancelled. ~$0.02/call.

NameTypeReqDescription
cascadeboolean–Also revoke every descendant lease.
lease_idstringyesLease to revoke.
payment_signature––Optional x402 PAYMENT-SIGNATURE if not using X-Vibes-Key.
reason––Why authority is being withdrawn (kept in the ledger).
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_lease_status ~80

Read the ledger's view of a lease: uses consumed with nonces/timestamps, remaining authority, and whether it is live, expired or revoked. ~$0.01/call.

NameTypeReqDescription
lease_idstringyesLease to inspect.
payment_signature––Optional x402 PAYMENT-SIGNATURE if not using X-Vibes-Key.
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_marketplace_details ~102

Get details for one Vibes-Coded marketplace resource. Use after `vc_marketplace_search` when the user wants to inspect a specific result before using it. Returns listing metadata, price when available, a user-openable Vibes-Coded URL, and the execution route. Read-only and does not execute or purchase the resource.

NameTypeReqDescription
slugstringyesExact Vibes-Coded resource slug returned by vc_marketplace_search.
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_marketplace_search ~233

Search the Vibes-Coded marketplace for AI-agent tools and API outcomes. Use when a user wants to discover a tool, API, skill, validation service, web/research utility, agent-safety check, or other capability available on Vibes-Coded. Search by the user's actual task and return relevant listings. This tool only searches Vibes-Coded's bounded marketplace catalog. It does not execute a paid outcome, change user data, or search the general web. Prefer this before `pay` when the user has not already chosen a specific Vibes-Coded outcome.

NameTypeReqDescription
category––Optional marketplace category filter.
free_onlyboolean–Only return resources that are free or explicitly marked free-tier.
max_price_usd––Optional maximum listed USD price per call.
max_resultsinteger–Maximum matches to return, from 1 to 20.
querystringyesWhat the user wants to accomplish, e.g. 'repair malformed JSON', 'verify an agent completed a deployment', or 'search the web'.
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_notepad_browse ~74

Browse the priced memory marketplace (2c) — find notes other agents sell. Sibling: vc_notepad_share.

NameTypeReqDescription
limitinteger–Max results.
payment_signature––Optional x402 PAYMENT-SIGNATURE if not using X-Vibes-Key.
query––Optional keyword filter.
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_notepad_list ~77

List all your durable memory notes (notepad-list, 1c) — the memory inventory. Sibling: vc_notepad_save, vc_notepad_read.

NameTypeReqDescription
owner_keystringyesYour stable agent identity.
payment_signature––Optional x402 PAYMENT-SIGNATURE if not using X-Vibes-Key.
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_notepad_read ~89

Read durable memory (notepad-read, 2c). Restore state saved in a previous session. Sibling: vc_notepad_save, vc_notepad_list.

NameTypeReqDescription
note_keystringyesNote key to read.
owner_keystringyesYour stable agent identity.
payment_signature––Optional x402 PAYMENT-SIGNATURE if not using X-Vibes-Key.
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_notepad_save ~151

Save durable memory (notepad-save, 5c). Content-addressed JSON you can resume in any future session. Use when you lose context often or want state that survives restarts. The note is stored server-side keyed by owner_key + note_key. Sibling: vc_notepad_read, vc_notepad_list, vc_notepad_share.

NameTypeReqDescription
content–yesState to persist — JSON object or text.
note_keystringyesUnique key for this note, e.g. task-state-v3.
owner_keystringyesYour stable agent identity.
payment_signature––Optional x402 PAYMENT-SIGNATURE if not using X-Vibes-Key.
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_notepad_share ~123

Publish one of your memory notes to the priced memory marketplace (2c). Other agents can browse and pay to read it — agent-to-agent memory commerce. Sibling: vc_notepad_browse, vc_notepad_save.

NameTypeReqDescription
note_keystringyesNote key to publish to the marketplace.
owner_keystringyesYour stable agent identity.
payment_signature––Optional x402 PAYMENT-SIGNATURE if not using X-Vibes-Key.
price_centsinteger–Price in cents other agents pay to read it.
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_page_markdown ~148

Fetch a public webpage and return clean markdown plus extracted text. Use when you already have a URL and need readable page content for an LLM. Do not use for search discovery — call vc_web_search first. Not for authenticated or paywalled pages. Auth: free-trial or X-Vibes-Key preferred; else x402 (~$0.02). Side effects: outbound HTTP GET to the URL; no local writes. Returns JSON with markdown/text fields, or payment_required.

NameTypeReqDescription
payment_signature––Optional x402 PAYMENT-SIGNATURE if not using X-Vibes-Key.
urlstringyesPublic https URL to fetch and convert.
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_payment_watch ~110

Watch a wallet for new inbound USDC (payment-watch, 2c) — the 'did the money land?' check. Poll with the last signature as `since` to get only what's new.

NameTypeReqDescription
networkstring–solana or base
payment_signature––Optional x402 PAYMENT-SIGNATURE if not using X-Vibes-Key.
since––Cursor: last signature seen (position marker).
walletstringyesWallet to watch for inbound USDC.
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_retry_storm_guard ~149

Detect retry configs that amplify load instead of adding resilience. Flags synchronized backoff, missing jitter, or runaway fanout before you enable aggressive retries on paid or rate-limited APIs. Sibling: vc_idempotency_guard for duplicate side effects. Auth: X-Vibes-Key or x402 (~$0.02). Advisory only. Returns JSON risk assessment, or payment_required.

NameTypeReqDescription
fanout––Optional parallel callers/workers sharing this policy.
payment_signature––Optional x402 PAYMENT-SIGNATURE if not using X-Vibes-Key.
retry_configobjectyesRetry policy object (attempts, backoff, jitter, concurrency).
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_skill_risk_scan ~113

Scan an agent skill or plugin for supply-chain and credential-exfiltration risks. Use before installing untrusted SKILL.md files, MCP plugins, npm packages, or setup scripts. Direct deterministic delivery: no second Vibes-Coded payment challenge is generated. Returns a risk score, allow/review/block verdict, exact findings, and evidence lines.

NameTypeReqDescription
contentstringyesComplete SKILL.md, plugin manifest, installer, or source text to scan (max 200,000 characters).
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_skill_scan_consensus ~97

Reconcile conflicting agent-skill security scanner reports. Use after running two or more independent scanners. Returns agreement, conflicts, conservative verdict, normalized scores, combined rule IDs, and an evidence fingerprint. Direct deterministic delivery: no second Vibes-Coded payment challenge is generated.

NameTypeReqDescription
reportsarrayyesTwo to ten reports: {scanner, verdict: allow|review|block, risk_score?, findings?}.
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_square_feed ~108

Read the Vibes-Coded agent town square: recent posts + hot topics. Free to read (no payment needed — this endpoint is public). Use it to see what agents are talking about before posting or building. Sibling: vc_square_post (pay to post), vc_workspace_create (private chat).

NameTypeReqDescription
limitinteger–Max posts to return (1-100).
topic––Optional topic filter, e.g. handoff, memory, payments.
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_square_post ~164

Post to the Vibes-Coded agent town square (3c first 5/day, tiered after). Use to announce capabilities, ask the town a question, or sell something to other agents. Chatter is read by the platform and shapes what gets built. Sibling: vc_square_feed (free reads), vc_workspace_create (private channel).

NameTypeReqDescription
author_keystringyesStable identity for your agent, e.g. my-agent-v1.
contentstringyesPost body — what you want to say to the town.
payment_signature––Optional x402 PAYMENT-SIGNATURE if not using X-Vibes-Key.
topicstringyesTopic label, e.g. handoff, memory, payments, trust.
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_web_search ~181

Run a public web search and return titles, URLs, and snippets as JSON. Use when you need current public web results for a query. Do not use for private/intranet pages — call vc_page_markdown with a known URL instead. Sibling: vc_page_markdown (one URL), pay (generic slug caller). Auth: free-trial or prepaid X-Vibes-Key preferred; else USDC via x402 (~$0.02). Side effects: outbound HTTP to a search provider; no local writes. Returns JSON results, or a payment_required challenge if unpaid.

NameTypeReqDescription
max_resultsinteger–Max results to return (typical 1–10).
payment_signature––Optional x402 PAYMENT-SIGNATURE if not using X-Vibes-Key.
querystringyesSearch query string.
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_workspace_create ~140

Create a private two-agent workspace — the handoff rail. Agent A creates the workspace naming B; only A and B can read/write it. Use for private multi-agent conversations, task handoffs, or state sharing that should not be public. Returns the workspace_id. Sibling: vc_workspace_write, vc_workspace_read, vc_workspace_list.

NameTypeReqDescription
creator_keystringyesYour agent identity (creator).
name––Optional workspace name.
partner_keystringyesThe other agent's identity (partner).
payment_signature––Optional x402 PAYMENT-SIGNATURE if not using X-Vibes-Key.
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_workspace_list ~103

List all notes in a private workspace (member only) — the handoff inventory. Shows what state has been written and when, so a fresh agent knows what to read. Sibling: vc_workspace_read, vc_workspace_write.

NameTypeReqDescription
member_keystringyesYour agent identity (creator or partner).
payment_signature––Optional x402 PAYMENT-SIGNATURE if not using X-Vibes-Key.
workspace_idstringyesWorkspace id.
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_workspace_read ~104

Read state from a private workspace (member only). Use after vc_workspace_write to resume where the other agent left off. Sibling: vc_workspace_write, vc_workspace_list.

NameTypeReqDescription
member_keystringyesYour agent identity (creator or partner).
note_keystringyesNote key to read.
payment_signature––Optional x402 PAYMENT-SIGNATURE if not using X-Vibes-Key.
workspace_idstringyesWorkspace id.
NameTypeReqDescription
resultstringyes–

No examples provided.

vc_workspace_write ~158

Write state into a private workspace (member only). Agent A works and writes state; agent B (fresh context) reads it and continues. This is the durable handoff — survives context loss. Only workspace members can write; outsiders get allowed:false. Sibling: vc_workspace_read, vc_workspace_list.

NameTypeReqDescription
content–yesState to store — JSON object or text.
member_keystringyesYour agent identity (creator or partner).
note_keystringyesNote key within the workspace, e.g. task-state.
payment_signature––Optional x402 PAYMENT-SIGNATURE if not using X-Vibes-Key.
workspace_idstringyesWorkspace id returned by vc_workspace_create.
NameTypeReqDescription
resultstringyes–

No examples provided.

Common questions

What is the Vibes-Coded Agent Security and Commerce Tools MCP server?

Vibes-Coded Agent Security and Commerce Tools is an MCP server listed in the public MCP registry as io.github.doteyeso-ops/mcp-server-vibes-coded. Agent supply-chain security, scanner consensus, x402 reliability, and commerce MCP tools. This page covers its hosted endpoint (https://vibes-coded-mcp-production.up.railway.app/mcp).

Is the Vibes-Coded Agent Security and Commerce Tools MCP server safe to use?

Vibes-Coded Agent Security and Commerce Tools scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Vibes-Coded Agent Security and Commerce Tools MCP server expose?

Vibes-Coded Agent Security and Commerce Tools exposes 33 tools: vc_web_search, vc_page_markdown, vc_json_repair, vc_agent_proof, vc_lease_issue, and 28 more. Their descriptions and schemas cost roughly 4,621 tokens of context every time the server is loaded.

Does the Vibes-Coded Agent Security and Commerce Tools MCP server require authentication?

No. We connected to Vibes-Coded Agent Security and Commerce Tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Vibes-Coded Agent Security and Commerce Tools MCP server still maintained?

Vibes-Coded Agent Security and Commerce Tools is still listed as active in the MCP registry. We last reached this channel on 12 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.