HubVibe: 38 Machine-Payable Dev Utilities and WCAG Audits
REMOTE · HUBVIBE-IO.COM · SCANNED SEP 25
Pay per call via HTTP 402: 5 site audits + 38 /work jobs as MCP tools and A2A skills, receipts
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 Security74
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4713 tokens (~109/item across 43 items; 43 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 Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 74% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "hubvibe_data_query" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 44 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 HubVibe: 38 Machine-Payable Dev Utilities and WCAG Audits MCP server?
HubVibe: 38 Machine-Payable Dev Utilities and WCAG Audits is a hosted endpoint at https://hubvibe-io.com/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 · hubvibe-io.com
claude mcp add --transport http its-fortunatefolly-hubvibe 'https://hubvibe-io.com/mcp'
{
"mcpServers": {
"its-fortunatefolly-hubvibe": {
"url": "https://hubvibe-io.com/mcp"
}
}
} {
"servers": {
"its-fortunatefolly-hubvibe": {
"type": "http",
"url": "https://hubvibe-io.com/mcp"
}
}
} [mcp_servers.its-fortunatefolly-hubvibe] url = "https://hubvibe-io.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"its-fortunatefolly-hubvibe": {
"type": "remote",
"url": "https://hubvibe-io.com/mcp",
"enabled": true
}
}
} openclaw mcp add its-fortunatefolly-hubvibe --url 'https://hubvibe-io.com/mcp' --transport streamable-http
mcp_servers:
its-fortunatefolly-hubvibe:
url: "https://hubvibe-io.com/mcp" {
"McpServers": {
"its-fortunatefolly-hubvibe": {
"Transport": "http",
"Url": "https://hubvibe-io.com/mcp"
}
}
} assistant mcp add its-fortunatefolly-hubvibe -t streamable-http -u 'https://hubvibe-io.com/mcp'
{
"mcpServers": {
"its-fortunatefolly-hubvibe": {
"type": "http",
"url": "https://hubvibe-io.com/mcp"
}
}
} 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.
- 25 Sept 26 +1
- 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
- The server rewrote its instructions, which are the text every model session reads security
- Tool coverage: 100% → 74% ▼ functional
- Schema quality: 190 → 109 ▲ functional
- Destructive annotations: pass → 0 functional
- Server version: 1.4.2 → 1.5.0 functional
- New tool “hubvibe_maps_places” functional
- New tool “hubvibe_chain_address” functional
- New tool “hubvibe_chain_network” functional
- New tool “hubvibe_chain_rpc” functional
- New tool “hubvibe_chain_transaction” functional
- New tool “hubvibe_code_execute” functional
- New tool “hubvibe_data_anomalies” functional
- New tool “hubvibe_data_forecast” functional
- New tool “hubvibe_data_query” functional
- New tool “hubvibe_data_question” functional
- New tool “hubvibe_extract_page” functional
- New tool “hubvibe_fetch_raw” functional
- New tool “hubvibe_image_generate” functional
- New tool “hubvibe_llm_analyze” functional
- New tool “hubvibe_llm_extract” functional
- New tool “hubvibe_llm_generate” functional
- New tool “hubvibe_maps_route” functional
- New tool “hubvibe_video_generate” functional
- New tool “hubvibe_verify_claims” functional
- New tool “hubvibe_speech_transcribe” functional
- New tool “hubvibe_speech_synthesize” functional
- New tool “hubvibe_security_mcp_inspect” functional
- New tool “hubvibe_search_web” functional
- New tool “hubvibe_research_web” functional
- New tool “hubvibe_research_page_facts” functional
- New tool “hubvibe_research_company” functional
- New tool “hubvibe_research_brief” functional
- New tool “hubvibe_prediction_market” functional
- New tool “hubvibe_prediction_events” functional
- New tool “hubvibe_monitor_snapshot” functional
- New tool “hubvibe_monitor_check” functional
- New tool “hubvibe_market_ticker” functional
- New tool “hubvibe_market_rates” functional
- New tool “hubvibe_market_quote” functional
- New tool “hubvibe_market_prediction” functional
- New tool “hubvibe_market_intel” functional
- New tool “hubvibe_maps_weather” functional
- 23 Sept 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 137 → 190 ▼ functional
- Server version: 1.4.1 → 1.4.2 functional
- New tool “hubvibe_predictive_probability_engine” functional
- 22 Sept 26 0
- Server version: 1.4.0 → 1.4.1 functional
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +2
- Tool “web_fetch” was removed ▼ security
- Tool “web_extract” was removed ▼ security
- Tool “prediction_markets” was removed ▼ security
- Tool “market_data” was removed ▼ security
- Tool “chain_rpc” was removed ▼ security
- Tool coverage: 68% → 100% ▲ functional
- Schema quality: 1280 → 687 ▲ functional
- Server version: 1.3.0 → 1.4.0 functional
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −1
- Tool coverage: 100% → 68% ▼ functional
- Schema quality: 687 → 1280 ▼ functional
- Server version: 1.2.0 → 1.3.0 functional
- New tool “chain_rpc” functional
- New tool “market_data” functional
- New tool “prediction_markets” functional
- New tool “web_extract” functional
- New tool “web_fetch” 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 25 Sept 2026 · Probed https://hubvibe-io.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hubvibe-io.com | CN=YE1,O=Let's Encrypt,C=US | 6 Sept 2026 | 5 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6616bab7f4fd20dd82cdcf12d3b976a48ca |
| SANs: hubvibe-io.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 hubvibe-io.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| hubvibe-io.com. | 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://hubvibe-io.com/mcp | Verified | 200 | |
| http (plaintext) | http://hubvibe-io.com/mcp | HTTPS enforced | 308 | https://hubvibe-io.com/mcp |
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 →
hubvibe_video_generate Generate a video ~141
Generate a short video from a text prompt using Veo. Off by default: enabled only once the operator has confirmed the configured Veo model resolves on this project (see the provider module for why). $10.00 per call. Returns: prompt, aspect_ratio, duration_seconds, video_base64 or gcs_uri, mime_type, model.
| Name | Type | Req | Description |
|---|---|---|---|
| aspect_ratio | string | – | 16:9 or 9:16. Default 16:9. |
| duration_seconds | integer | – | 4, 6 or 8. Default 6. |
| generate_audio | boolean | – | Default false. |
| prompt | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| billing_warning | string | – | Present only when the charge was recorded with a caveat. |
| price_usd | number | yes | What this call cost, in USD. |
| provenance | object | yes | How the result was produced: which providers ran and how long each took. |
| receipt_id | string | yes | Receipt id for this job. |
| receipt_url | string | yes | Where to fetch the machine-readable receipt (free, no payment). |
| result | object | yes | – |
| status | string | yes | Present only on a delivered result. |
| worker | string | yes | Catalog name of the worker that ran. |
No examples provided.
What is the HubVibe: 38 Machine-Payable Dev Utilities and WCAG Audits MCP server?
HubVibe: 38 Machine-Payable Dev Utilities and WCAG Audits is an MCP server listed in the public MCP registry as io.github.Its-fortunatefolly/hubvibe. Pay per call via HTTP 402: 5 site audits + 38 /work jobs as MCP tools and A2A skills, receipts. This page covers its hosted endpoint (https://hubvibe-io.com/mcp).
Is the HubVibe: 38 Machine-Payable Dev Utilities and WCAG Audits MCP server safe to use?
HubVibe: 38 Machine-Payable Dev Utilities and WCAG Audits scores 76 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 HubVibe: 38 Machine-Payable Dev Utilities and WCAG Audits MCP server expose?
HubVibe: 38 Machine-Payable Dev Utilities and WCAG Audits exposes 43 tools: audit_wcag, audit_seo, audit_security, audit_performance, audit_bundle, and 38 more. Their descriptions and schemas cost roughly 4,610 tokens of context every time the server is loaded.
Does the HubVibe: 38 Machine-Payable Dev Utilities and WCAG Audits MCP server require authentication?
No. We connected to HubVibe: 38 Machine-Payable Dev Utilities and WCAG Audits without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the HubVibe: 38 Machine-Payable Dev Utilities and WCAG Audits MCP server still maintained?
HubVibe: 38 Machine-Payable Dev Utilities and WCAG Audits is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.