hs-femtech-mcp
Anchors SHA-256 hashes of registry entries to the Bitcoin blockchain via OpenTimestamps, enabling provable timestamping and tamper-evidence for verified sources.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@hs-femtech-mcpList verified information sources on menopause in the UK."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.

HORIZON SHIELD Femtech Registry
A neutral, verifiable registry of femtech (women's health) information sources. It does not diagnose, does not claim products work, does not take referral fees, and does not pretend to be a medical authority. It verifies who stands behind a source, under which jurisdiction, with what compensation, and lets anyone re-compute the proof.
Live endpoint: https://femtech.horizonshield.dev (also https://hs-femtech-mcp.oga-surf-project.workers.dev)
Verified
This server passes the HORIZON SHIELD Verification Gate (status: verified): reachable, MCP conformant, agent-card published, compensation disclosed (paid_by: public, no referral or listing fees), and deterministic. It holds itself to the same bar it would apply to anyone else. Re-check it yourself, no trust in us required:
curl -s -X POST "https://hs-verify-gate.oga-surf-project.workers.dev/check" \
-H "content-type: application/json" \
-d '{"endpoint":"https://femtech.horizonshield.dev/"}'Related MCP server: ebp-directory
Why this exists
Women's health is a credence-goods market: buyers cannot easily judge quality, and noise, advertising and referral-driven "recommendations" crowd out primary sources. As front LLMs start recommending femtech, the hard problem is not more content, it is trust: who published this, are they authoritative, do they get paid to say it, and can the claim be re-checked?
This server is the trust rail, not the oracle. It never becomes the medical authority. It indexes authoritative sources and makes their provenance, jurisdiction and compensation machine-readable and re-computable.
The design principle: do not call "verified" what you cannot verify. We verify existence, authority tier, jurisdiction, disclosure and re-computability. We do not adjudicate medical truth.
What it does / does not
Does
Indexes femtech information sources with publisher, authority tier, jurisdiction, evidence URL and machine-readable compensation.
Verifies each entry deterministically (SHA-256) so a third party can re-compute the proof.
Returns neutral, source-linked general information, always with a disclaimer.
Discloses its own compensation (
referral_fee: false,listing_fee: false) and passes its own bar at/self.
Does not (enforced in code, fail-closed)
Diagnose (no symptom to condition tool).
Claim a product is effective, or rank brands.
Recommend or take referral / listing fees for any source.
Store personal health data.
Claim medical authority or make cross-jurisdiction medical judgments.
The registry model
Each entry is one information source:
{
"entry_id": "acog_pms_en",
"kind": "source",
"publisher": "American College of Obstetricians and Gynecologists (ACOG)",
"authority_tier": "A_public_or_academic",
"jurisdiction": "US",
"lang": "en",
"topic": "pms",
"evidence_url": "https://www.acog.org/",
"compensation": { "paid_by": "none", "referral_fee": false, "listing_fee": false },
"status": "verified",
"verified_at": "2026-08-27T22:46:08.179Z",
"provenance_sha256": "…",
"anchored": false
}Five conditions to be listed (self-application plus machine verification, no human gatekeeper):
A reachable, real evidence source.
A declared authority tier (public / academic, medical institution, commercial media).
A declared jurisdiction (so no source is treated as "correct everywhere").
Machine-readable compensation disclosure (we do not judge the content, we only remove the option to hide it).
Determinism and re-computation (SHA-256 anchored, reproducible by anyone).
A source that fails is not "rejected", it is pending. Fix it and re-apply.
Topics (P1)
menstruation · pms · menopause, with authoritative sources across JP / US / GB
(JSOG, Japan Society for Menopause and Women's Health, MHLW Healthcare Lab, ACOG, NHS, The Menopause Society, Office on Women's Health).
Quickstart
Self-check (the server declares and proves its own neutrality):
BASE="https://hs-femtech-mcp.oga-surf-project.workers.dev"
curl -s "$BASE/self" | python3 -m json.toolList the registry (filter by topic / jurisdiction / lang / status):
curl -s "$BASE/registry?topic=menopause" | python3 -m json.toolMCP over JSON-RPC 2.0:
curl -s -X POST "$BASE/" -H "content-type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
curl -s -X POST "$BASE/" -H "content-type: application/json" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"get_femtech_topic","arguments":{"topic_id":"pms_basics_en"}}}'Agent discovery: GET /.well-known/agent-card.json (A2A) and GET /llms.txt (for front LLMs).
Tools
tool | read only | purpose |
| no | validate a source against the 5 conditions, persist if verified |
| yes | filter and list entries |
| yes | one entry with provenance |
| yes | canonical form + SHA-256, fail-closed |
| yes | neutral, source-linked information |
| yes | product category explainer, no brand, no efficacy |
| yes | reproduce the hash yourself |
| yes | A2A card with compensation disclosure |
Verifiability
Every entry has a canonical JSON form and a SHA-256 that a third party can re-compute (how_to_verify). Verified entries are listed at /anchor/pending for Bitcoin / JIDEC anchoring (OpenTimestamps), so untamperedness becomes provable with a timestamp. verified means untampered and re-computable, never medically true.
Not a medical service
This service provides source verification and general information only. It does not diagnose, treat, or recommend products. For symptoms or treatment decisions, consult a healthcare professional.
About
Built and operated by The HORIZ音s株式会社, part of HORIZON SHIELD. Same design lineage as the JCCDB open construction-cost dataset and the HORIZON SHIELD verification gate: verifiable, buyer-side, no pay-for-endorsement.
Endpoints
method | path | purpose |
POST |
| MCP JSON-RPC (initialize, tools/list, tools/call) |
GET |
| liveness |
GET |
| neutrality declaration and self-check |
GET |
| registry index |
GET |
| hashes awaiting Bitcoin / JIDEC anchoring |
GET |
| front-LLM guidance |
GET |
| A2A agent card |
License
MIT. See LICENSE.
This server cannot be installed
Maintenance
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables contributing, challenging, discovering, verifying, and querying contestable public records from AI coding tools via MCP.6461MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for querying a cross-referenced directory of evidence-based therapies and interventions, enabling search by query, tier, problem, population, modality, and registry.1
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to securely access, query, and mutate normalized user-controlled health data (e.g., from Apple Health or Supabase) through a bounded set of MCP tools, with optional OAuth and sandboxed deployment.MIT
Related MCP Connectors
Remote MCP for MCP consent scope receipt, structured receipts, audit logs, and reviewer-ready eviden
The evidence layer for MCP: live operational grades plus Trust Receipts for every registry server.
Remote MCP for C2PA intake verifier MCP, structured receipts, audit logs, and reviewer-ready evidenc
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ogasurfproject-jpg/hs-femtech-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server