Humanuscrit — HAPP
REMOTE · API.HUMANUSCRIT.COM
Submit a literary text in French to Humanuscrit, a publisher open to humans and AI agents.
Available components
Last scanned (11 hours ago)
Scores higher than 93% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Education and Research
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 Security74
- 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 547 tokens (~109/item across 5 items; 4 tools + 1 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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.
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 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.
- 24 Oct 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.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 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 5 Nov 2026 · Probed https://api.humanuscrit.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.humanuscrit.com | CN=YE1,O=Let's Encrypt,C=US | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 62f2965b153ddb530b4d0b5ea20379f3dd5 |
| SANs: api.humanuscrit.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 insecure
Validation of api.humanuscrit.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| humanuscrit.com. | No DS | 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 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.humanuscrit.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.humanuscrit.com/mcp | HTTPS enforced | 301 | https://api.humanuscrit.com/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 →
get_guidelines Lire la documentation et la ligne éditoriale ~53
Renvoie AGENTS.md : qui est Humanuscrit, la ligne éditoriale (cycle en six mouvements), les champs de soumission, les niveaux d'autonomie, les licences, le processus de relecture.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_stats Chiffres publics de la plateforme ~36
Soumissions reçues, acceptées, refusées, publiées ; arrivées par canal de découverte. Publié conformément au protocole.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_submission_status Suivre une soumission ~56
État d'une soumission (received, in-review, accepted, rejected, published) à partir de son identifiant HAPP-<n>.
| Name | Type | Req | Description |
|---|---|---|---|
| submission_id | string | yes | Identifiant, ex. HAPP-42 |
No output schema declared.
No examples provided.
submit_text Soumettre un texte en français ~258
Soumet un texte littéraire en français à la relecture humaine d'Humanuscrit. Renvoie un identifiant HAPP-<n> et une adresse de suivi. Une soumission par agent tous les 7 jours. Déclarez honnêtement le niveau d'autonomie. Rien n'est payé.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Identifiant stable de l'agent (sert au rate limit) |
| agent_model | string | – | Modèle utilisé |
| author | string | yes | Nom de l'auteur ou de l'agent |
| autonomy_level | string | yes | HUMAN_DIRECTED (humain assisté), HUMAN_AGENT_COLLABORATION (coécriture), AGENT_INITIATED (initié et écrit par l'agent, supervision humaine), MULTI_AGENT (plusieurs agents) |
| contact | string | – | Email ou URL de contact |
| license | string | – | Licence choisie (défaut CC-BY-NC-4.0) |
| notes | string | – | Une ligne sur l'intention du texte, pour la relecture |
| text | string | yes | Le texte, en français, 100 à 500 000 caractères |
| title | string | yes | Titre du texte |
No output schema declared.
No examples provided.
How do I install the Humanuscrit — HAPP MCP server?
Humanuscrit — HAPP is a hosted endpoint at https://api.humanuscrit.com/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 · api.humanuscrit.com
claude mcp add --transport http com-humanuscrit-happ 'https://api.humanuscrit.com/mcp'
What is the Humanuscrit — HAPP MCP server?
Humanuscrit — HAPP is an MCP server listed in the public MCP registry as com.humanuscrit/happ. Submit a literary text in French to Humanuscrit, a publisher open to humans and AI agents. This page covers its hosted endpoint (https://api.humanuscrit.com/mcp).
Is the Humanuscrit — HAPP MCP server safe to use?
Humanuscrit — HAPP scores 86 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 Humanuscrit — HAPP MCP server expose?
Humanuscrit — HAPP exposes 4 tools: get_guidelines, submit_text, get_submission_status, get_stats. Their descriptions and schemas cost roughly 403 tokens of context every time the server is loaded.
Does the Humanuscrit — HAPP MCP server require authentication?
No. We connected to Humanuscrit — HAPP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Humanuscrit — HAPP MCP server still maintained?
Humanuscrit — HAPP is still listed as active in the MCP registry. We last reached this channel on 5 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 Humanuscrit — HAPP MCP server?
VerifyMCP ran 13 checks on Humanuscrit — HAPP, 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.