io.github.paxton888/basecite
REMOTE · MCP.BASECITE.COM · SCANNED SEP 20
Tenant-scoped evidence intake and controlled AI context over MCP.
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 Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 364 tokens (~45/item across 8 items; 3 tools + 5 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the io.github.paxton888/basecite MCP server?
io.github.paxton888/basecite is a hosted endpoint at https://mcp.basecite.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 · mcp.basecite.com
claude mcp add --transport http paxton888-basecite 'https://mcp.basecite.com/mcp'
{
"mcpServers": {
"paxton888-basecite": {
"url": "https://mcp.basecite.com/mcp"
}
}
} {
"servers": {
"paxton888-basecite": {
"type": "http",
"url": "https://mcp.basecite.com/mcp"
}
}
} [mcp_servers.paxton888-basecite] url = "https://mcp.basecite.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"paxton888-basecite": {
"type": "remote",
"url": "https://mcp.basecite.com/mcp",
"enabled": true
}
}
} openclaw mcp add paxton888-basecite --url 'https://mcp.basecite.com/mcp' --transport streamable-http
mcp_servers:
paxton888-basecite:
url: "https://mcp.basecite.com/mcp" {
"McpServers": {
"paxton888-basecite": {
"Transport": "http",
"Url": "https://mcp.basecite.com/mcp"
}
}
} assistant mcp add paxton888-basecite -t streamable-http -u 'https://mcp.basecite.com/mcp'
{
"mcpServers": {
"paxton888-basecite": {
"type": "http",
"url": "https://mcp.basecite.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.
- 20 Sept 26 71
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 20 Sept 2026 · Probed https://mcp.basecite.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=basecite.com | CN=WE1,O=Google Trust Services,C=US | 16 Aug 2026 | 14 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | ab9b010c85fdadb70e959bb4d7347c66 |
| SANs: basecite.com, mcp.basecite.com, *.mcp.basecite.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.basecite.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| basecite.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | default-src 'none'; frame-ancestors 'none'; base-uri 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.basecite.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.basecite.com/mcp | Served over HTTP | 200 |
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 →
basecite_get_ai_context ~76
Return one bounded customer/solution-company submitted AI context record by org_id and upload_id with provenance and not_evaluated fields. No raw file download, list-all, bulk export, truth verification, company verification, or ranking claim is returned.
| Name | Type | Req | Description |
|---|---|---|---|
| org_id | string | yes | – |
| upload_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| ai_context | object | – | – |
| not_evaluated | array | – | – |
| org_id | string | – | – |
| provenance | object | – | – |
| status | string | – | – |
| upload_id | string | – | – |
No examples provided.
basecite_get_capabilities ~58
Return the machine-readable capabilities and integration boundaries of the BaseCite service. This tool never returns customer data and requires no credential.
| Name | Type | Req | Description |
|---|---|---|---|
| include_boundaries | boolean | – | Include the public safety and data-access boundaries in the capabilities response. |
| Name | Type | Req | Description |
|---|---|---|---|
| authentication | string | – | – |
| boundaries | array | – | – |
| capabilities | array | – | – |
| customer_data | string | – | – |
| documentation | string | – | – |
| public_resources | boolean | – | – |
| service | string | – | – |
No examples provided.
basecite_get_public_discovery ~64
Return BaseCite public developer, API, MCP, registry, and safety-boundary links. This tool never returns customer data and requires no credential.
| Name | Type | Req | Description |
|---|---|---|---|
| include_registry | boolean | – | Include the Smithery and Official MCP Registry links in the public discovery response. |
| Name | Type | Req | Description |
|---|---|---|---|
| boundaries | array | – | – |
| developer_docs | string | – | – |
| mcp_endpoint | string | – | – |
| official_registry | string | – | – |
| openapi | string | – | – |
| registry | string | – | – |
| sdk | string | – | – |
| service | string | – | – |
| website | string | – | – |
No examples provided.
What is the io.github.paxton888/basecite MCP server?
io.github.paxton888/basecite is an MCP server listed in the public MCP registry as io.github.paxton888/basecite. Tenant-scoped evidence intake and controlled AI context over MCP. This page covers its hosted endpoint (https://mcp.basecite.com/mcp).
Is the io.github.paxton888/basecite MCP server safe to use?
io.github.paxton888/basecite scores 71 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.github.paxton888/basecite MCP server expose?
io.github.paxton888/basecite exposes 3 tools: basecite_get_public_discovery, basecite_get_capabilities, basecite_get_ai_context. Their descriptions and schemas cost roughly 198 tokens of context every time the server is loaded.
Does the io.github.paxton888/basecite MCP server require authentication?
Yes. io.github.paxton888/basecite asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.paxton888/basecite MCP server still maintained?
io.github.paxton888/basecite 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.