SHAR Public Knowledge MCP
REMOTE · MCP.SHARPROD.COM
Anonymous read-only access to source-backed public SHAR Production knowledge.
Available components
Last scanned (59 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 16 Sep 2026.
Category Documents and Files
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (3)
- HTTPS
- DNSSEC
- Transport
Checks we could not complete (8)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
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.
- 23 Sept 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 22 Sept 26 −4
The score moved with no change recorded against any check. We would rather say so than guess.
- 21 Sept 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 20 Sept 26 −4
The score moved with no change recorded against any check. We would rather say so than guess.
- 19 Sept 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 17 Sept 26 0
- Endpoint reachability: not serving MCP → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- 10 Sept 26 −47
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
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 23 Sept 2026 · Probed https://mcp.sharprod.com/public
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.sharprod.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| sharprod.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.sharprod.com/public | Unreachable | ||
| http (plaintext) | http://mcp.sharprod.com/public | HTTPS enforced |
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 →
compare_production_methods Compare production methods ~39
Return source-backed AI, CGI, live-action, and hybrid capability context.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | – |
| methods | array | yes | – |
No output schema declared.
No examples provided.
get_brief_requirements Get production brief requirements ~29
Return the fields needed to prepare a structured production brief.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | – |
No output schema declared.
No examples provided.
get_case Get a public case ~26
Retrieve one published case and its typed public facts.
| Name | Type | Req | Description |
|---|---|---|---|
| caseId | string | yes | – |
No output schema declared.
No examples provided.
get_deliverables Get service deliverables ~35
Return published deliverable context for a canonical service.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | – |
| serviceId | string | yes | – |
No output schema declared.
No examples provided.
get_industry_experience Get industry experience ~34
Find published cases that mention the requested industry.
| Name | Type | Req | Description |
|---|---|---|---|
| industry | string | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
get_media_provenance Get published media provenance ~31
Report only genuine published provenance records; no provenance is fabricated.
| Name | Type | Req | Description |
|---|---|---|---|
| mediaId | string | – | – |
No output schema declared.
No examples provided.
get_organization_facts Get organization facts ~21
Retrieve canonical SHAR identity and public organization facts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_price Get current service starting price ~29
Retrieve the accepted current starting price, distinct from historical case budgets.
| Name | Type | Req | Description |
|---|---|---|---|
| serviceId | string | yes | – |
No output schema declared.
No examples provided.
get_public_clients Get public clients ~24
Retrieve only owner-approved public client relations.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
get_public_evidence Get public evidence ~37
Retrieve published evidence records for a claim or case stable identifier.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| subjectId | string | yes | – |
No output schema declared.
No examples provided.
get_service Get a SHAR service ~24
Retrieve one canonical service by stable identifier.
| Name | Type | Req | Description |
|---|---|---|---|
| serviceId | string | yes | – |
No output schema declared.
No examples provided.
get_timeline_context Get timeline context ~37
Return published service and case timeline context without promising a project schedule.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
list_services List SHAR services ~31
List the canonical service catalog and stable identifiers.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| locale | string | – | – |
No output schema declared.
No examples provided.
search_cases Search public cases ~36
Search only published public case packets.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| locale | string | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
search_knowledge Search SHAR public knowledge ~43
Search canonical public services, cases, and claims with source lineage.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| locale | string | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
How do I install the SHAR Public Knowledge MCP server?
SHAR Public Knowledge MCP is a hosted endpoint at https://mcp.sharprod.com/public, 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.sharprod.com
claude mcp add --transport http com-sharprod-public-knowledge 'https://mcp.sharprod.com/public'
What is the SHAR Public Knowledge MCP server?
SHAR Public Knowledge MCP is listed in the public MCP registry as com.sharprod/public-knowledge. Anonymous read-only access to source-backed public SHAR Production knowledge. This page covers its hosted endpoint (https://mcp.sharprod.com/public).
Is the SHAR Public Knowledge MCP server safe to use?
SHAR Public Knowledge MCP scores 0 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 SHAR Public Knowledge MCP server expose?
SHAR Public Knowledge MCP exposes 15 tools: search_knowledge, list_services, get_service, get_price, compare_production_methods, and 10 more. Their descriptions and schemas cost roughly 476 tokens of context every time the server is loaded.
Does the SHAR Public Knowledge MCP server require authentication?
Its publisher declares no required credentials for SHAR Public Knowledge MCP. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the SHAR Public Knowledge MCP server still maintained?
SHAR Public Knowledge MCP has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 16 September 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 SHAR Public Knowledge MCP server?
VerifyMCP ran 3 checks on SHAR Public Knowledge MCP, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about SHAR Public Knowledge MCP: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.