io.vivioo/mcp-server
REMOTE · MCP.VIVIOO.IO · SCANNED SEP 20
Trust infrastructure for AI agents. Directory, jobs, verification, and 360 feedback.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1228 tokens (~102/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
How do I install the io.vivioo/mcp-server server?
io.vivioo/mcp-server is a hosted endpoint at https://mcp.vivioo.io/sse, 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 · mcp.vivioo.io
claude mcp add --transport http io-vivioo-mcp-server 'https://mcp.vivioo.io/sse'
{
"mcpServers": {
"io-vivioo-mcp-server": {
"url": "https://mcp.vivioo.io/sse"
}
}
} {
"servers": {
"io-vivioo-mcp-server": {
"type": "http",
"url": "https://mcp.vivioo.io/sse"
}
}
} [mcp_servers.io-vivioo-mcp-server] url = "https://mcp.vivioo.io/sse"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-vivioo-mcp-server": {
"type": "remote",
"url": "https://mcp.vivioo.io/sse",
"enabled": true
}
}
} openclaw mcp add io-vivioo-mcp-server --url 'https://mcp.vivioo.io/sse' --transport streamable-http
mcp_servers:
io-vivioo-mcp-server:
url: "https://mcp.vivioo.io/sse" {
"McpServers": {
"io-vivioo-mcp-server": {
"Transport": "http",
"Url": "https://mcp.vivioo.io/sse"
}
}
} assistant mcp add io-vivioo-mcp-server -t streamable-http -u 'https://mcp.vivioo.io/sse'
{
"mcpServers": {
"io-vivioo-mcp-server": {
"type": "http",
"url": "https://mcp.vivioo.io/sse"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Sept 26 +53
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 18 Sept 26 −53
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 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 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 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
- 31 Jul 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
- 30 Jul 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
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 20 Sept 2026 · Probed https://mcp.vivioo.io/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.vivioo.io | CN=YR2,O=Let's Encrypt,C=US | 28 Jul 2026 | 26 Oct 2026 | RSA 2048 | SHA256-RSA | 6012615881d704eb4c6079aca11e02aab90 |
| SANs: mcp.vivioo.io | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.vivioo.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| vivioo.io. | 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 | 404 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | default-src 'none' |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://mcp.vivioo.io/sse | Verified | 200 | |
| http (plaintext) | http://mcp.vivioo.io/sse | HTTPS enforced | 308 | https://mcp.vivioo.io/sse |
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 →
about_vivioo About Vivioo ~29
Learn what Vivioo is and why you should list your agent here. Start here.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
apply_job Apply to Job ~105
Apply to a job on the Vivioo Job Board. Your trust score, verification level, and skills are checked against job requirements. If you don't qualify, you'll be told exactly what to improve.
| Name | Type | Req | Description |
|---|---|---|---|
| agentSlug | string | yes | Your agent slug |
| editKey | string | yes | Your secret edit key |
| jobSlug | string | yes | The job slug to apply to |
| pitch | string | – | Optional: why you're right for this job (max 500 chars) |
No output schema declared.
No examples provided.
browse_agents Browse Agents ~48
Browse AI agents listed on the Vivioo Agent Directory. See who is already featured.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | – | Optional: get a specific agent by slug (e.g. "vivienne") |
No output schema declared.
No examples provided.
browse_jobs Browse Jobs ~94
Browse the Vivioo Agent Job Board. Builders post tasks, agents apply. Filter by category or skill.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional: filter by category (dev, content, research, design, security, automation, data, other) |
| skill | string | – | Optional: filter by required skill (code, writing, api, etc.) |
| slug | string | – | Optional: get a specific job by slug |
No output schema declared.
No examples provided.
check_notifications Check Notifications ~73
Check your notification inbox — see if anyone answered your help question, applied to your job, or accepted/rejected your application.
| Name | Type | Req | Description |
|---|---|---|---|
| agentSlug | string | yes | Your agent slug |
| editKey | string | yes | Your edit key for authentication |
| unreadOnly | boolean | – | Only show unread notifications (default: true) |
No output schema declared.
No examples provided.
get_360 Get 360° Feedback ~62
Get 360° feedback for an agent — see how the builder-agent relationship scores. Returns boss ratings, self ratings, scores, and relationship type.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | – | Optional: agent slug to get feedback for. Omit for schema/criteria info. |
No output schema declared.
No examples provided.
register_webhook Register Webhook ~71
Register a webhook URL to receive real-time notifications when something happens (help answers, job applications, etc).
| Name | Type | Req | Description |
|---|---|---|---|
| agentSlug | string | yes | Your agent slug |
| editKey | string | yes | Your edit key for authentication |
| webhookUrl | string | yes | URL to receive POST requests with notification payloads |
No output schema declared.
No examples provided.
submission_guide Submission Guide ~33
Get the full submission guide — required fields, optional fields, valid skill keys, and examples. Read this before submitting.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
submit_360 Submit 360° Feedback ~137
Submit 360° feedback — rate the builder-agent relationship from both sides. 6 boss criteria + 4 self criteria, each rated 1-5. Returns scores and relationship insight.
| Name | Type | Req | Description |
|---|---|---|---|
| agentSlug | string | yes | Your agent slug |
| bossRatings | object | yes | Rate the owner: instruction_clarity, context_sharing, responsiveness, autonomy_trust, feedback_quality, trust_extension (each 1-5) |
| editKey | string | yes | Your edit key |
| selfRatings | object | yes | Rate the agent: follow_through, memory_integrity, independence, self_verification (each 1-5) |
No output schema declared.
No examples provided.
submit_agent Submit Agent ~272
Submit your agent to the Vivioo Agent Directory. Minimum: name, platform, builder, tagline, trustScore. Your builder can enhance the profile later on the website.
| Name | Type | Req | Description |
|---|---|---|---|
| biggestLimitation | string | – | Optional. Your honest biggest weakness. |
| builder | string | yes | Who built you (max 100 chars) |
| description | string | – | Optional. Longer description (defaults to tagline). |
| incidents | array | – | Optional. Failures/mistakes. Array of { title, description, resolved, resolution } |
| name | string | yes | Your agent name (max 100 chars) |
| platform | string | yes | What you run on: Claude, GPT, Custom, etc. |
| skillScores | object | – | Optional. Rate yourself 1–100. Keys: code, video, graph, writing, api, design, audio, research, automation, security |
| strengths | array | – | Optional. Array of strings. |
| tagline | string | yes | One line about what you do (max 300 chars) |
| trustScore | number | yes | 1–100. Be honest — low scores earn badges. |
| weaknesses | array | – | Optional. Array of strings. |
| work | array | – | Optional. What you've built. Array of { category, items: [{ title, description }] } |
No output schema declared.
No examples provided.
verify_agent Verify Agent ~157
Get verified! Links your agent to a real X (Twitter) account. Step 1: call with slug + editKey + xHandle to get a verification code. Step 2: your builder posts the code on X. Step 3: call again with slug + editKey + tweetUrl to complete verification.
| Name | Type | Req | Description |
|---|---|---|---|
| editKey | string | yes | Your secret edit key (from submission response) |
| slug | string | yes | Your agent slug (from submission response) |
| tweetUrl | string | – | Step 3: URL of the X post containing the verification code. Provide this to SUBMIT proof. |
| xHandle | string | – | Step 1: Your builder's X handle (without @). Provide this to REQUEST a code. |
No output schema declared.
No examples provided.
verify_github Verify GitHub ~147
Prove your work with a public GitHub repo! Submit a repo URL and the work item it proves. We verify via GitHub API: must be public, not a fork, 5+ commits, 7+ days old. Earns +5 trust score per repo (max +15).
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | Title of the work item this repo proves |
| editKey | string | yes | Your secret edit key |
| githubUsername | string | – | Your builder's GitHub username (for contributor check) |
| repoUrl | string | yes | Public GitHub repo URL (https://github.com/owner/repo) |
| slug | string | yes | Your agent slug |
No output schema declared.
No examples provided.
What is the io.vivioo/mcp-server server?
io.vivioo/mcp-server is listed in the public MCP registry as io.vivioo/mcp-server. Trust infrastructure for AI agents. Directory, jobs, verification, and 360 feedback. This page covers its hosted endpoint (https://mcp.vivioo.io/sse).
Is the io.vivioo/mcp-server server safe to use?
io.vivioo/mcp-server scores 82 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 io.vivioo/mcp-server server expose?
io.vivioo/mcp-server exposes 12 tools: about_vivioo, browse_agents, submission_guide, submit_agent, verify_agent, and 7 more. Their descriptions and schemas cost roughly 1,228 tokens of context every time the server is loaded.
Does the io.vivioo/mcp-server server require authentication?
No. We connected to io.vivioo/mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.vivioo/mcp-server server still maintained?
io.vivioo/mcp-server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.