Creditable
REMOTE · CREDITABLE.VC
Read builder program facts, validate applications and submit founder-approved projects for review.
Available components
Last scanned (just now)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 323 tokens (~107/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 70
First indexed and scored.
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 5 Nov 2026 · Probed https://creditable.vc/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=creditable.vc | CN=YR2,O=Let's Encrypt,C=US | 5 Oct 2026 | 3 Jan 2027 | RSA 2048 | SHA256-RSA | 6d2462273d70c1104b45bd7352e93d1dd01 |
| SANs: creditable.vc | ||||||
| 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 creditable.vc. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| vc. | present | 40792 | 8 | Verified |
| creditable.vc. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://creditable.vc/mcp | Verified | 200 | |
| http (plaintext) | http://creditable.vc/mcp | HTTPS enforced | 308 | https://creditable.vc/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 →
read_program ~39
Read Creditable’s published builder offer and submission rules. No cash check size, duration, funding guarantee or review deadline is published. Applying creates no commitment.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
submit_project ~171
Send an actual founder-approved startup submission to Creditable’s private review queue. Requires explicit confirmation, founder_authorized:true and review/contact consent. Reuse the exact UUID and body after a timeout. Success requires saved:true and a reference; it is not selection or funding. No files are uploaded through MCP; authorized material links are supported.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmSubmission | boolean | yes | True only after the founder approves sending these exact details/materials to Creditable for review and follow-up. |
| idempotencyKey | string | yes | New UUID for a new application; preserve it and the exact body for identical retries. |
| submission | object | yes | All strings are trimmed. Agent submissions must set submitted_by.founder_authorized=true after the founder approves review and follow-up. No eligibility restrictions on stage, sector or country. |
No output schema declared.
No examples provided.
validate_submission ~76
Check founder-approved project details against the existing intake schema without saving or sending an application. Does not return the applicant’s personal details.
| Name | Type | Req | Description |
|---|---|---|---|
| submission | object | yes | All strings are trimmed. Agent submissions must set submitted_by.founder_authorized=true after the founder approves review and follow-up. No eligibility restrictions on stage, sector or country. |
No output schema declared.
No examples provided.
How do I install the Creditable MCP server?
Creditable is a hosted endpoint at https://creditable.vc/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 · creditable.vc
claude mcp add --transport http theguysaccount-creditable 'https://creditable.vc/mcp'
What is the Creditable MCP server?
Creditable is an MCP server listed in the public MCP registry as io.github.theguysaccount/creditable. Read builder program facts, validate applications and submit founder-approved projects for review. This page covers its hosted endpoint (https://creditable.vc/mcp).
Is the Creditable MCP server safe to use?
Creditable scores 73 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 Creditable MCP server expose?
Creditable exposes 3 tools: read_program, validate_submission, submit_project. Their descriptions and schemas cost roughly 286 tokens of context every time the server is loaded.
Does the Creditable MCP server require authentication?
No. We connected to Creditable without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Creditable MCP server still maintained?
Creditable is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.