io.github.jyswee/fleetstreet
REMOTE · MCP.FLEETSTREET.AI · SCANNED SEP 20
License your creative work to AI on your terms, and run your creator business. 46 tools, keyless.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (fleetstreet_signup). See how to fix → View diagnostics → Fail
- 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
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 214 tokens (~107/item across 2 items; 2 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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.github.jyswee/fleetstreet MCP server?
io.github.jyswee/fleetstreet is a hosted endpoint at https://mcp.fleetstreet.ai/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.fleetstreet.ai
claude mcp add --transport http jyswee-fleetstreet 'https://mcp.fleetstreet.ai/sse'
{
"mcpServers": {
"jyswee-fleetstreet": {
"url": "https://mcp.fleetstreet.ai/sse"
}
}
} {
"servers": {
"jyswee-fleetstreet": {
"type": "http",
"url": "https://mcp.fleetstreet.ai/sse"
}
}
} [mcp_servers.jyswee-fleetstreet] url = "https://mcp.fleetstreet.ai/sse"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jyswee-fleetstreet": {
"type": "remote",
"url": "https://mcp.fleetstreet.ai/sse",
"enabled": true
}
}
} openclaw mcp add jyswee-fleetstreet --url 'https://mcp.fleetstreet.ai/sse' --transport streamable-http
mcp_servers:
jyswee-fleetstreet:
url: "https://mcp.fleetstreet.ai/sse" {
"McpServers": {
"jyswee-fleetstreet": {
"Transport": "http",
"Url": "https://mcp.fleetstreet.ai/sse"
}
}
} assistant mcp add jyswee-fleetstreet -t streamable-http -u 'https://mcp.fleetstreet.ai/sse'
{
"mcpServers": {
"jyswee-fleetstreet": {
"type": "http",
"url": "https://mcp.fleetstreet.ai/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.
- 1 Sept 26 +1
- Stability: 0.97 → pass security
- 30 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.
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 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
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 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
- 3 Aug 26 0
- Stability: unverified → 0.03 ▲ 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.fleetstreet.ai/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fleetstreet.ai | CN=YR1,O=Let's Encrypt,C=US | 31 Jul 2026 | 29 Oct 2026 | RSA 4096 | SHA256-RSA | 50d2892c58c8b52d52d08e2170a922de860 |
| SANs: *.fleetstreet.ai, fleetstreet.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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.fleetstreet.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| fleetstreet.ai. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://mcp.fleetstreet.ai/sse | Verified | 200 | |
| http (plaintext) | http://mcp.fleetstreet.ai/sse | HTTPS enforced | 301 | https://mcp.fleetstreet.ai/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 →
fleetstreet_get_started ~32
Explains what fleetstreet is and how to activate this MCP server (no API key on this session yet).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fleetstreet_signup ~182
Create a new fleetstreet portfolio site. Requires the human's email and a portfolio/studio name: a welcome + activation email is sent to them (card required via Stripe to start the 7-day free trial, nothing charged during it). Returns an API key (shown once) and unlocks all fleetstreet tools in this session immediately. Ask the human for their email and portfolio name before calling.
| Name | Type | Req | Description |
|---|---|---|---|
| bandName | string | yes | The portfolio / studio / artist name, e.g. "Jane Doe Photography". Used as the site name and to derive the slug. |
| string | yes | Human email. The welcome + activation link is sent here. | |
| firstName | string | – | The human's first name (optional; used to personalise the welcome email). |
| genre | string | – | Optional discipline (photography, illustration, mixed-media, …). |
No output schema declared.
No examples provided.
What is the io.github.jyswee/fleetstreet MCP server?
io.github.jyswee/fleetstreet is an MCP server listed in the public MCP registry as io.github.jyswee/fleetstreet. License your creative work to AI on your terms, and run your creator business. 46 tools, keyless. This page covers its hosted endpoint (https://mcp.fleetstreet.ai/sse).
Is the io.github.jyswee/fleetstreet MCP server safe to use?
io.github.jyswee/fleetstreet 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 io.github.jyswee/fleetstreet MCP server expose?
io.github.jyswee/fleetstreet exposes 2 tools: fleetstreet_get_started, fleetstreet_signup. Their descriptions and schemas cost roughly 214 tokens of context every time the server is loaded.
Does the io.github.jyswee/fleetstreet MCP server require authentication?
No. We connected to io.github.jyswee/fleetstreet without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.jyswee/fleetstreet MCP server still maintained?
io.github.jyswee/fleetstreet 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.