Skip to content

Regga MCP server

ai.regga/reggaregga.aistreamable-httpv1.0.4Scanned

When AI say no take a scecond look

1 tool: 1 only read.

Tools: 0 delete, 0 irreversible, 0 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Sign-in required, OAuth metadata published. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Regga MCP server can do

The Regga MCP server is published by regga.ai, a domain the MCP Registry verified. It has 1 tool. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

1 tool brings in text other people can write (check_a_no).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint asks for sign-in and publishes OAuth metadata, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 1.0.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

1 tool

Only reads 1Show 1 read-only tool
  • check_a_noSearches for things that an answer said do not exist or cannot be done: products, apps, services, competitors, ways to do something (guides, workarounds, open-source fixes, procedu…Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Searches for things that an answer said do not exist or cannot be done: products, apps, services, competitors, ways to do something (guides, workarounds, open-source fixes, procedures), or evidence about a factual "no" ("no study shows...", "that's not allowed", "you're not entitled to..."). Suited to questions such as "is there an app / tool / service that...", "are there competitors to...", "is there a way to...", "does X exist in my country / in my language / on Shopify", or a factual or rights question whose answer is "no". It runs the given queries in parallel on the general web and, optionally, inside specific places: app stores (Apple App Store, Google Play, Chrome Web Store), plugin marketplaces (Shopify, WordPress), launch and startup sites (Product Hunt and others), social and business pages (LinkedIn, Facebook, Instagram), how-to sites and forums (Reddit, YouTube, GitHub, Stack Exchange, local-language forums), and facts / research / rights sources (Wikipedia, PubMed, arXiv, government and rights sites). Parameters: - claim: the "no" being checked. - product_shape: what the product or method would do, for whom, through which channel or device. - queries: 4-20 varied queries (synonyms, functional descriptions, "alternatives to X", "how to X", "X workaround"), in English and the user's language. - marketplace_queries: 3-5 short keyword phrases (2-5 words, English) run inside each chosen place, e.g. "memoir WhatsApp bot". - places: only the places that fit the question (apps/tools -> app_stores, plugin_marketplaces, launch_and_startup_sites, social_and_business_pages; "how to" -> how_to_and_forums; laws, rights, research -> facts_research_and_rights). Fewer places is faster and cheaper. Returns deduplicated results (title, URL, snippet, where found) and a coverage report: queries run, places searched and skipped, hits per place. A result has not been verified; "not found" in these places is not proof that something does not exist.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
    • title: Check a 'no' from the AI: find products, apps, competitors, ways to do it or counter-evidence

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, OAuth metadata published

Looked at Nov 17, 2026, 15:18 UTC, unchanged since Nov 17, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
401
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
yes
resource_metadata in WWW-Authenticate
https://regga.ai/.well-known/oauth-protected-resource/signin/mcp
RFC 9728 protected resource metadata
https://regga.ai/.well-known/oauth-protected-resource/signin/mcp
Authorization servers
https://regga.ai
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff
    • Changed:check_a_noOnly readsdescriptioninputSchema

Install

Pinned to version 1.0.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http regga https://regga.ai/mcp
claude mcp add --transport http regga https://regga.ai/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__regga__check_a_no"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as regga. Review it before you use it.

Capability tags behind 1 rule
  • mcp__regga__check_a_no untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ai.regga/regga/verify?hash=40b1a11aa473ff30c41916fa26d3b9ddfb8140b0a6c9b953696b67b8b320c0c9" | jq -e '.changed == false'

Pinned hash 40b1a11aa473, from Nov 20, 2026, 10:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.regga/regga/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.regga/regga
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.regga/regga.svg)](https://radar.anlyon.com/servers/ai.regga/regga)

Source: MCP Registry. Synced Nov 20, 2026, 10:17 UTC.

Regga MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Regga MCP server safe?

No scan can promise that. What its definitions show: 1 tool, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the Regga MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Regga MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Regga MCP server have?

1 tool: 1 read. check_a_no.

Does the Regga MCP server need sign-in or OAuth?

Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.

Does the Regga MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Regga MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.