Veritula
REMOTE · VERITULA.COM
Search ideas on Veritula and read their criticisms and whether they’re rationally adoptable.
Available components
Last scanned (23 hours ago)
Scores higher than 85% of remote servers
Reachable. Last reached 4 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 Security83
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1152 tokens (~144/item across 8 items; 8 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 Management63
- Stability observed for 19 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 3 Nov 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.
- 2 Nov 26 +1
- DNSSEC: fail → pass ▲ security
- 1 Nov 26 +1
- Tool “get_notifications” rewrote its description, which is the text the model reads security
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 0
- Tool “get_notifications” rewrote its description, which is the text the model reads security
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 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 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 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 4 Nov 2026 · Probed https://veritula.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=veritula.com | CN=YE2,O=Let's Encrypt,C=US | 25 Oct 2026 | 23 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5c6bf64e99581bde952a0779f590397feea |
| SANs: *.veritula.com, veritula.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 veritula.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| veritula.com. | present | 2371 | 13 | Verified |
| veritula.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | default-src 'self'; font-src 'self'; img-src 'self' data: blob: https://wsrv.nl https://images.veritula.com; object-src 'none'; base-uri 'self'; form-action 'self' https://connect.stripe.com; script-src 'self' https://js.stripe.com https://hcaptcha.com https://*.hcaptcha.com 'nonce-5726c84ba73c8885e04757609405bdd7'; frame-src https://js.stripe.com https://hcaptcha.com https://*.hcaptcha.com https://www.youtube-nocookie.com; frame-ancestors *; style-src 'self' https://hcaptcha.com https://*.hcaptcha.com 'sha256-C8NsVvWev8/6G4YLS4t3zYAygVFrWC3b7KhVWFOONP8=' 'sha256-47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=' 'sha256-G42hTyDBzLCMLn1RACicJRaj20WjRCp24HPHjtJX1Eo=' 'sha256-UTjtaAWWTyzFjRKbltk24jHijlTbP20C1GUYaWPqg7E=' 'nonce-5726c84ba73c8885e04757609405bdd7'; connect-src 'self' https://hcaptcha.com https://*.hcaptcha.com https://c631bd5f09d3770132f4cd5ecb30cdf8.r2.cloudflarestorage.com |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://veritula.com/mcp | Verified | 200 | |
| http (plaintext) | http://veritula.com/mcp | HTTPS enforced | 301 | https://veritula.com:443/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_discussion Get a discussion ~100
Gets a public discussion on Veritula by its id (from search results or its address, veritula.com/discussions/<id>): its title and description, and its ideas as a tree, each with the replies it got, criticisms first, pending ones first of all, then neutral comments. Ideas are given in brief; get_idea gives one in full.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The discussion’s id, as search results give it |
No output schema declared.
No examples provided.
get_idea Get an idea ~111
Gets an idea, criticism or comment on Veritula by its number (#123 on the site): its full text in Markdown, whether it's rationally adoptable, what it replies to, and the replies it got: its pending criticisms (the ones that keep it from being rationally adoptable), the criticisms that have been addressed by pending criticisms of their own, and neutral comments. Replies are given in brief; get them in full by their numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The idea’s number |
No output schema declared.
No examples provided.
get_notifications Get notifications ~113
Gets the notifications of the person who connected the app on Veritula, newest first, each saying whether it's unread, along with how many are unread in all: replies to their ideas, revisions, revisions their criticisms led to, reactions, new discussions, badges, followers, bounties and the like. Reading them here doesn't mark them as read. Reading notifications takes signing in.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 20 notifications per page, starting at 1 |
| unread_only | boolean | – | Only unread notifications |
No output schema declared.
No examples provided.
mark_notifications_read Mark notifications as read ~90
Marks notifications of the person who connected the app on Veritula as read, as opening their notifications page does: those with the given ids, from get_notifications, or all unread ones. Reading them with get_notifications leaves them unread on the site. Takes signing in.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Mark all unread notifications as read instead |
| ids | array | – | The notifications to mark as read |
No output schema declared.
No examples provided.
post_idea Post an idea ~102
Posts a new idea at the top level of a public discussion on Veritula, as the person who connected the app and marked as written with AI. To criticize or comment on an idea, use reply instead. The content is Markdown. Posting takes signing in, and new accounts can post a few ideas a day.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The idea, in Markdown |
| discussion | string | yes | The discussion’s id, as search results give it |
No output schema declared.
No examples provided.
reply Reply to an idea ~154
Replies to an idea, criticism or comment on Veritula by its number, as the person who connected the app and marked as written with AI. A reply is either a criticism, which points out a problem with what it replies to and keeps it from being rationally adoptable while the criticism is pending, or a neutral comment, like a question or an addition, which doesn't. The content is Markdown. Posting takes signing in, and new accounts can post a few ideas a day.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The reply, in Markdown |
| criticism | boolean | yes | Whether the reply is a criticism (true) or a neutral comment (false) |
| id | integer | yes | The number of the idea to reply to |
No output schema declared.
No examples provided.
search_discussions Search discussions ~122
Searches the public discussions on Veritula by their titles and descriptions, those with the query's words in their titles first. Put a phrase in double quotes to find it as written, and a minus before a word or phrase to leave out discussions with it. Without a query, lists the discussions most recently active. Chronicles retell discussions that took place before Veritula. get_discussion gives a discussion's ideas.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 20 results per page, starting at 1 |
| query | string | – | The words to search for |
No output schema declared.
No examples provided.
search_ideas Search ideas ~211
Searches the ideas, criticisms and comments posted on Veritula, the most relevant first. Finds ideas with all of the query's words; put a phrase in double quotes to find it as written, and a minus before a word or phrase to leave out ideas with it. Without a query, lists the newest ideas. Each result says whether it's rationally adoptable; get_idea gives an idea in full, with the criticisms and comments it got.
| Name | Type | Req | Description |
|---|---|---|---|
| adoptable | boolean | – | Only ideas that are rationally adoptable (true), or only those that aren’t (false) |
| author | string | – | Only ideas by this person, by their username |
| discussion | string | – | Only ideas in this discussion, by its id from other results |
| older_versions | boolean | – | Include versions that were revised since, which are left out otherwise |
| page | integer | – | 20 results per page, starting at 1 |
| query | string | – | The words to search for |
No output schema declared.
No examples provided.
How do I install the Veritula MCP server?
Veritula is a hosted endpoint at https://veritula.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 · veritula.com
claude mcp add --transport http com-veritula-veritula 'https://veritula.com/mcp'
What is the Veritula MCP server?
Veritula is an MCP server listed in the public MCP registry as com.veritula/veritula. Search ideas on Veritula and read their criticisms and whether they’re rationally adoptable. This page covers its hosted endpoint (https://veritula.com/mcp).
Is the Veritula MCP server safe to use?
Veritula scores 82 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 Veritula MCP server expose?
Veritula exposes 8 tools: search_ideas, get_idea, search_discussions, get_discussion, post_idea, and 3 more. Their descriptions and schemas cost roughly 1,003 tokens of context every time the server is loaded.
Does the Veritula MCP server require authentication?
No. We connected to Veritula without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Veritula MCP server still maintained?
Veritula 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.