Profullstack
REMOTE · PROFULLSTACK.COM
153 read-only tools from 15 Profullstack MCP servers: domains, SEO, public data, feeds, podcasts
Available components
Last scanned (23 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Search and Retrieval
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
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 19341 tokens (~125/item across 154 items; 154 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 77% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 154 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 155 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +16
- HSTS header: unverified → fail ▼ security
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.27 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- “r4ck_cheapest” added an optional parameter “new” cosmetic
- “r4ck_facets” added an optional parameter “new” cosmetic
- “r4ck_search_servers” added an optional parameter “new” cosmetic
- 18 Nov 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 16 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.13 → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 15 Nov 26 0
- Tool “nichedb_where_to_buy_book” rewrote its description, which is the text the model reads security
- New tool “nichedb_find_product” functional
- “r4ck_cheapest” reworded the description of “stock” cosmetic
- “r4ck_facets” reworded the description of “stock” cosmetic
- “r4ck_search_servers” reworded the description of “stock” cosmetic
- 14 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.
- 12 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 11 Nov 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 21 Nov 2026 · Probed https://profullstack.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=profullstack.com | CN=YE2,O=Let's Encrypt,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 63d823d8c126095a9a0c2048f1cdb76a824 |
| SANs: profullstack.com, www.profullstack.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of profullstack.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| profullstack.com. | DS published | 2371 | 13 | Verified |
| profullstack.com. | Verified address RRset verified with the apex keys |
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 |
|---|---|---|---|---|
| streamable-http | https://profullstack.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://profullstack.com/api/mcp | HTTPS enforced | 301 | https://profullstack.com/api/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 →
w3bs_w3bs_run W3BS: Render W3BS Template ~74
[W3BS] Run the deterministic template runtime with explicit consent. Produces rendered instructions; never calls a model or tool. Served by W3BS (https://w3bs.org).
| Name | Type | Req | Description |
|---|---|---|---|
| consent | boolean | – | – |
| inputs | object | – | – |
| uri | string | yes | – |
No output schema declared.
No examples provided.
w3bs_w3bs_search W3BS: Search W3BS Artifacts ~57
[W3BS] Search the registry for versioned W3BS resources. Served by W3BS (https://w3bs.org).
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | – |
| type | string | – | – |
No output schema declared.
No examples provided.
w3bs_w3bs_verify W3BS: Verify W3BS Signature ~59
[W3BS] Verify the manifest signature against pinned publisher keys and current revocation state. This does not authorize execution. Served by W3BS (https://w3bs.org).
| Name | Type | Req | Description |
|---|---|---|---|
| uri | string | yes | – |
No output schema declared.
No examples provided.
wx93_expand_link wx93: Expand Short Link ~47
[wx93] Where a wx93.me short link goes, without following it. Served by wx93 (https://wx93.me/docs).
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Profullstack MCP server?
Profullstack is a hosted endpoint at https://profullstack.com/api/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 · profullstack.com
claude mcp add --transport http com-profullstack-profullstack 'https://profullstack.com/api/mcp'
What is the Profullstack MCP server?
Profullstack is an MCP server listed in the public MCP registry as com.profullstack/profullstack. 153 read-only tools from 15 Profullstack MCP servers: domains, SEO, public data, feeds, podcasts. This page covers its hosted endpoint (https://profullstack.com/api/mcp).
Is the Profullstack MCP server safe to use?
Profullstack scores 74 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 Profullstack MCP server expose?
Profullstack exposes 154 tools: profullstack_craigslist, profullstack_seo-ranking, profullstack_wcag, profullstack_fleet_list_services, profullstack_fleet_get_service, and 149 more. Their descriptions and schemas cost roughly 19,074 tokens of context every time the server is loaded.
Does the Profullstack MCP server require authentication?
No. We connected to Profullstack without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Profullstack MCP server still maintained?
Profullstack is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Profullstack MCP server?
VerifyMCP ran 13 checks on Profullstack, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.