io.github.GavinLee1/mcp-fleet
REMOTE · MCP-FLEET.NEBULA-LABS.ONLINE
12 MCP tools: invoice→JSON, text→SQL, PII redaction, regex & more. Free to try, pay per call.
Available components
Last scanned (22 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Developer Tools
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 648 tokens (~54/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 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
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
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.
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 30 Oct 26 0
- Stability: 0.97 → pass security
- 29 Oct 26 0
- Stability: pass → 0.97 functional
- 26 Oct 26 +4
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- 25 Oct 26 −4
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- 14 Oct 26 0
- Stability: 0.97 → pass security
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 −1
No change was recorded against any check on this day. Stability & Change Management went from 97 to 93.
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 4 Nov 2026 · Probed https://mcp-fleet.nebula-labs.online/mcp/sse?src=mcp_registry
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nebula-labs.online | CN=WE1,O=Google Trust Services,C=US | 9 Oct 2026 | 7 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | b9acc468c7f8e4bc0ea187ac55d0df67 |
| SANs: nebula-labs.online, *.nebula-labs.online | ||||||
| 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-fleet.nebula-labs.online. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| online. | present | 30961 | 13 | Verified |
| nebula-labs.online. | 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 |
|---|---|---|---|---|
| sse | https://mcp-fleet.nebula-labs.online/mcp/sse?src=mcp_registry | Verified | 200 | |
| http (plaintext) | http://mcp-fleet.nebula-labs.online/mcp/sse?src=mcp_registry | 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 →
code_explain ~38
Explain what a code snippet does, step by step, with complexity and risk notes.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The source code to explain. |
No output schema declared.
No examples provided.
cron_explain ~52
Explain a cron expression in plain English and list the next run times.
| Name | Type | Req | Description |
|---|---|---|---|
| cron_expression | string | yes | A standard 5-field cron expression, e.g. '30 9 * * 1-5'. |
No output schema declared.
No examples provided.
email_draft ~43
Turn bullet points or a brief into a polished professional email (subject + body).
| Name | Type | Req | Description |
|---|---|---|---|
| brief | string | yes | Bullet points or a short brief describing the email to write. |
No output schema declared.
No examples provided.
invoice_pdf_to_json ~76
Convert raw invoice text (extracted from PDF, email, or image OCR) into a structured JSON object. Returns vendor, date, line items, totals, and currency in a machine-readable format.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_text | string | yes | The raw text content of the invoice. Can be messy — include all text exactly as extracted. |
No output schema declared.
No examples provided.
json_schema_infer ~44
Infer a JSON Schema (draft 2020-12) from a sample JSON document.
| Name | Type | Req | Description |
|---|---|---|---|
| sample_json | string | yes | A sample JSON document (object or array). |
No output schema declared.
No examples provided.
meeting_summarize ~41
Summarize a meeting transcript into a summary, action items, decisions, and participants.
| Name | Type | Req | Description |
|---|---|---|---|
| transcript | string | yes | The raw meeting transcript or notes. |
No output schema declared.
No examples provided.
pii_redact ~63
Locally detect and redact high-confidence PII (emails, phones, SSNs, credit cards, IPs) from text — raw data never leaves the server. Returns redacted text and found entities.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Text that may contain personal data. |
No output schema declared.
No examples provided.
regex_builder ~41
Build a regular expression from a plain-language description, with an explanation and test cases.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | What the regex should match, in plain language. |
No output schema declared.
No examples provided.
sentiment_analyze ~40
Analyze sentiment of text with an overall score and per-aspect breakdown.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The text to analyze (review, message, feedback). |
No output schema declared.
No examples provided.
text_to_compliance_checklist ~124
Convert a block of requirement, regulation, or specification text into a structured compliance checklist. Each checklist item includes a category, obligation, priority (HIGH/MEDIUM/LOW), and verification method.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Optional: additional context about the industry or use case (e.g. 'SaaS company, GDPR jurisdiction, healthcare data'). Helps the model assign more accurate priorities. |
| requirement_text | string | yes | The requirement or specification text to analyze. Can be a contract clause, regulatory text, internal policy, or any document describing obligations. |
No output schema declared.
No examples provided.
text_to_sql ~46
Convert a natural-language data question into a SQL query. Returns the SQL, dialect, and tables used.
| Name | Type | Req | Description |
|---|---|---|---|
| request | string | yes | Natural-language question, optionally with a schema description. |
No output schema declared.
No examples provided.
unit_test_outline ~40
Generate a unit-test outline (cases + coverage targets) for a function.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The function or module to generate test cases for. |
No output schema declared.
No examples provided.
How do I install the io.github.GavinLee1/mcp-fleet server?
io.github.GavinLee1/mcp-fleet is a hosted endpoint at https://mcp-fleet.nebula-labs.online/mcp/sse?src=mcp_registry, 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-fleet.nebula-labs.online
claude mcp add --transport http gavinlee1-mcp-fleet 'https://mcp-fleet.nebula-labs.online/mcp/sse?src=mcp_registry'
What is the io.github.GavinLee1/mcp-fleet server?
io.github.GavinLee1/mcp-fleet is listed in the public MCP registry as io.github.GavinLee1/mcp-fleet. 12 MCP tools: invoice→JSON, text→SQL, PII redaction, regex & more. Free to try, pay per call. This page covers its hosted endpoint (https://mcp-fleet.nebula-labs.online/mcp/sse?src=mcp_registry).
Is the io.github.GavinLee1/mcp-fleet server safe to use?
io.github.GavinLee1/mcp-fleet scores 68 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.GavinLee1/mcp-fleet server expose?
io.github.GavinLee1/mcp-fleet exposes 12 tools: invoice_pdf_to_json, text_to_compliance_checklist, text_to_sql, json_schema_infer, regex_builder, and 7 more. Their descriptions and schemas cost roughly 648 tokens of context every time the server is loaded.
Does the io.github.GavinLee1/mcp-fleet server require authentication?
No. We connected to io.github.GavinLee1/mcp-fleet without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.GavinLee1/mcp-fleet server still maintained?
io.github.GavinLee1/mcp-fleet is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.