Rumoro
REMOTE · MCP.RUMORO.DEV
Track what people say about your product on Reddit, X, Hacker News, GitHub and more
Available components
Last scanned (5 minutes ago)
Scores higher than 99% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 11971 tokens (~202/item across 59 items; 57 tools + 2 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 Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% 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
- All 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 59 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.
- 4 Nov 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.
- 2 Nov 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.
- 31 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.
- 29 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.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 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 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 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 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 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 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 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://mcp.rumoro.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.rumoro.dev | CN=YR1,O=Let's Encrypt,C=US | 28 Sept 2026 | 27 Dec 2026 | RSA 2048 | SHA256-RSA | 5667cd66f08a49dfe7c68404d4d31c9c496 |
| SANs: mcp.rumoro.dev | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.rumoro.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| rumoro.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="rumoro-mcp", resource_metadata="https://mcp.rumoro.dev/.well-known/oauth-protected-resource"
Bearer realm="rumoro-mcp", resource_metadata="https://mcp.rumoro.dev/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | frame-ancestors 'self'; base-uri 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), browsing-topics=() |
Protected resource metadata
| Document | https://mcp.rumoro.dev/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.rumoro.dev/mcp |
| Authorisation server | https://app.rumoro.dev/api/auth |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.rumoro.dev/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.rumoro.dev/mcp | HTTPS enforced | 308 | https://mcp.rumoro.dev/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 →
update_group Update group ~192
Changes a keyword group's name, its externalId or its company description in context. Null clears externalId. Null clears context too, so the workspace profile applies again, and new mentions use the change right away. The default group can be renamed but takes no description, because it is the workspace itself and uses the company profile (update_company).
| Name | Type | Req | Description |
|---|---|---|---|
| context | – | – | Sets a new company description for the group. Null removes it, and the workspace profile applies again. New mentions use it right away, and older ones are not scored again. The default group cannot h… |
| externalId | – | – | Sets a new external id. Null removes it. |
| id | string | yes | The group's id (grp_...) |
| name | string | – | The group's name, such as a client, campaign or product. Must be unique in the workspace. |
No output schema declared.
No examples provided.
update_keyword Update keyword ~829
Changes a keyword. You can rename it with term: the new term is tracked from now on, with no look-back, and the keyword keeps its id, settings and what the old term found. You can set its platforms (a list, or null for all), mute or unmute it, change its kind, or set its classifier context (null clears it). You can change its matching rules, where each field is optional and an empty list clears it, with requiredTerms and requiredMode any or all, excludedTerms with a `*` wildcard at either end, excludedAuthors and caseSensitive. You can set its monthly cap with cap: { mentions: N }, where null removes it and a cap above this month's count resumes a capped keyword right away. You can move it with groupId, which returns 409 if that group already has the term. You can set reviewSources, the full list of App Store, Google Play, Trustpilot or Google Maps pages, where an empty list disconnects them and a newly added app or country brings its last 30 days free. You can replace the RSS or Atom feeds it reads with feeds, the whole list of { url }, where an empty list disconnects them and a newly added feed brings its newest 10 matching items of the last 30 days. You can switch comments on or off with comments ({ enabled, maxPerPost }; $0.008 per comment delivered). Rules only affect new mentions. Returns the keyword after the change, with its stats.
| Name | Type | Req | Description |
|---|---|---|---|
| cap | – | – | Sets a new monthly mention cap, or null for no cap. A cap above this month's count resumes a capped keyword right away. A cap at or below the count pauses it. |
| comments | object | – | Comments under this keyword's mentions; omitted fields stay as they are (on create: off, 20 per mention). |
| context | – | – | Up to 300 characters the classifier reads for this keyword only, in addition to the company profile or the group's description. Say what the term means for you and what to ignore, for example "Basil… |
| feeds | array | – | RSS or Atom feeds this keyword reads, at most 20, each { url }: a feed's address, or a page's (a forum, a community, a blog), whose advertised feed is used, else a usual address such as /feed or /rss… |
| groupId | string | – | Target group (grp_...). 409 if it already has this term. |
| id | string | yes | The keyword's id |
| kind | string | – | New kind (brand, competitor or topic). |
| matching | object | – | Fields you leave out stay as they are. An empty list clears a field. |
| muted | boolean | – | Muting stops polling and matching. Existing mentions are kept. |
| platforms | – | – | Sets a new platform list. Null means all platforms. An empty list means none, which works when the keyword has reviewSources and only collects reviews. |
| reviewSources | array | – | Sets a new list of review pages for this keyword. An empty list disconnects them all, and their reviews are kept. A page or country you add gets the free 30-day look-back. Pages already listed are un… |
| term | string | – | A new term for the keyword. It keeps its id, settings and the mentions the old term found, and the new term is tracked from now on, with no look-back. A 409 when its group already tracks the new term. |
No output schema declared.
No examples provided.
update_mention Update mention ~369
The only way to change a mention. Set status to "ignored" when it is not interesting, "done" when handled, or "open" to reopen it. Assign it with assigneeId, or null to remove the assignment. Hide it from the feed until an ISO 8601 time with snoozedUntil, or null to bring it back. Add a team note with note, or null to remove it. Correct the classifier with `relevant`, where true or false sets relevance to 100 or 0 and moves the mention into or out of the relevant feed, and null removes your judgment. `sentiment` sets the label, and null brings back the classifier's. Use these corrections when the user says a mention is noise or was missed. Fields you leave out stay as they are. Delivery and billing never change.
| Name | Type | Req | Description |
|---|---|---|---|
| assigneeId | – | – | The user id of a workspace member, or null to remove the assignment. |
| id | string | yes | Mention id (mm_...) |
| note | – | – | A note for your team. Null or an empty string removes it. |
| relevant | boolean|null | – | Set it to override the classifier, or null to restore the classifier's score. true means relevance 100, and a filtered mention joins the relevant feed. false means 0, and it leaves. Billing is unaffe… |
| sentiment | – | – | The sentiment you choose. Null removes it and brings back the classifier's. |
| snoozedUntil | – | – | Hides the mention from the feed until this time, given as ISO 8601 or epoch ms. Send null to bring it back now. |
| status | string | – | ignored or done marks it handled, and open reopens it. |
No output schema declared.
No examples provided.
update_person Update person ~145
Changes your workspace's details on a person. You can set their full tag list, notes, mute, the outreach owner (ownerId, a member's user id, or null to remove) and stage. Muting hides their posts from the feed and all channels. Collection and billing do not change.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The person's id (aut_...) |
| muted | boolean | – | – |
| notes | string | – | – |
| ownerId | – | – | The user id of the member responsible for this contact. Null removes it. |
| stage | string | – | The outreach stage your team has reached with this person. |
| tags | array | – | Sets the full new list. |
No output schema declared.
No examples provided.
update_segment Update segment ~68
Changes a saved segment's name, description or filter. `filter` sets the full new filter.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| filter | object | – | Sets the full new filter. |
| id | string | yes | The segment's id (seg_...) |
| name | string | – | – |
No output schema declared.
No examples provided.
update_view Update view ~68
Changes a saved view's name, description or filter. `filter` sets the full new filter.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| filter | object | – | Sets the full new filter. |
| id | string | yes | The view's id (vw_...) |
| name | string | – | – |
No output schema declared.
No examples provided.
whoami Whoami ~65
Returns the workspace this credential works in, the kind of credential (an API key or an OAuth sign-in), whether it can write, and the signed-in user if there is one. Call it once when a session starts, to name the workspace and learn whether write tools will work.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Rumoro MCP server?
Rumoro is a hosted endpoint at https://mcp.rumoro.dev/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 · mcp.rumoro.dev
claude mcp add --transport http dev-rumoro-mcp 'https://mcp.rumoro.dev/mcp'
What is the Rumoro MCP server?
Rumoro is an MCP server listed in the public MCP registry as dev.rumoro/mcp. Track what people say about your product on Reddit, X, Hacker News, GitHub and more. This page covers its hosted endpoint (https://mcp.rumoro.dev/mcp).
Is the Rumoro MCP server safe to use?
Rumoro scores 92 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 Rumoro MCP server expose?
Rumoro exposes 57 tools: list_segments, create_segment, update_segment, delete_segment, list_views, and 52 more. Their descriptions and schemas cost roughly 11,815 tokens of context every time the server is loaded.
Does the Rumoro MCP server require authentication?
Yes. Rumoro asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Rumoro MCP server still maintained?
Rumoro 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.