# io.github.paxton888/basecite (remote · mcp.basecite.com)

Tenant-scoped evidence intake and controlled AI context over MCP.

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.basecite.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/paxton888-basecite/mcp.md), [page](https://verifymcp.io/servers/paxton888-basecite/mcp)

## Channel facts

- Endpoint: `https://mcp.basecite.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 364 tokens (~45/item across 8 items; 3 tools + 5 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 50% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http paxton888-basecite 'https://mcp.basecite.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "paxton888-basecite": {
      "url": "https://mcp.basecite.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "paxton888-basecite": {
      "type": "http",
      "url": "https://mcp.basecite.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.paxton888-basecite]
url = "https://mcp.basecite.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "paxton888-basecite": {
      "type": "remote",
      "url": "https://mcp.basecite.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add paxton888-basecite --url 'https://mcp.basecite.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  paxton888-basecite:
    url: "https://mcp.basecite.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "paxton888-basecite": {
      "Transport": "http",
      "Url": "https://mcp.basecite.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add paxton888-basecite -t streamable-http -u 'https://mcp.basecite.com/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 71)

First indexed and scored.

## MCP tools (3)

### `basecite_get_public_discovery` (~64 tokens)

Return BaseCite public developer, API, MCP, registry, and safety-boundary links. This tool never returns customer data and requires no credential.

Input parameters:

- `include_registry` (boolean): Include the Smithery and Official MCP Registry links in the public discovery response.

Output parameters:

- `boundaries` (array)
- `developer_docs` (string)
- `mcp_endpoint` (string)
- `official_registry` (string)
- `openapi` (string)
- `registry` (string)
- `sdk` (string)
- `service` (string)
- `website` (string)

### `basecite_get_capabilities` (~58 tokens)

Return the machine-readable capabilities and integration boundaries of the BaseCite service. This tool never returns customer data and requires no credential.

Input parameters:

- `include_boundaries` (boolean): Include the public safety and data-access boundaries in the capabilities response.

Output parameters:

- `authentication` (string)
- `boundaries` (array)
- `capabilities` (array)
- `customer_data` (string)
- `documentation` (string)
- `public_resources` (boolean)
- `service` (string)

### `basecite_get_ai_context` (~76 tokens)

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.

Input parameters:

- `org_id` (string, required)
- `upload_id` (string, required)

Output parameters:

- `ai_context` (object)
- `not_evaluated` (array)
- `org_id` (string)
- `provenance` (object)
- `status` (string)
- `upload_id` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/paxton888-basecite/mcp#diagnostics

## Score history

- 2026-09-20: 71

## Common questions

### 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.

## Links

- Remote endpoint: https://mcp.basecite.com/mcp
- Repository: https://github.com/paxton888/basecite-agent-discovery
- Changelog RSS feed: https://verifymcp.io/servers/paxton888-basecite/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/paxton888-basecite/mcp.json
- HTML version of this page: https://verifymcp.io/servers/paxton888-basecite/mcp