Skip to content

mcp-registry-uptime

link.hultra/mcp-registry-uptimehultra.linkstreamable-httpv1.0.1Scanned

Annuaire vérifié des serveurs MCP : ce qui est mort, protégé ou en retard de spec.

5 tools: 5 change things.

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

Tools listed without sign-in. Remote posture

With Anlyon

5 tools here change things. Govern them.

  • 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 mcp-registry-uptime can do

The mcp-registry-uptime is published by hultra.link, a domain the MCP Registry verified. It has 5 tools. It can create or change data (5 tools: cherche_capacite, etat_serveur, config_pour, changements and 1 more), but cannot delete data. None of its tools only reads.

1 tool can send data out of your system (etat_serveur).

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

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 1.0.1.

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.

5 tools

Changes things 5Claude Code: ask
  • changementsMorts, nouveaux et changements de spec depuis une date (AAAA-MM-JJ).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Morts, nouveaux et changements de spec depuis une date (AAAA-MM-JJ).
  • cherche_capaciteServeurs MCP vivants correspondant à un besoin, avec leur version de spec.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Serveurs MCP vivants correspondant à un besoin, avec leur version de spec.
  • config_pourBloc de configuration prêt à coller pour un serveur.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Bloc de configuration prêt à coller pour un serveur.
  • etat_protocolesCompte des entrées par protocole mesuré.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Compte des entrées par protocole mesuré.
  • etat_serveurSanté, version de spec et portée de la vérification d'un serveur, par URL.Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Santé, version de spec et portée de la vérification d'un serveur, par URL.

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 untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
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.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:15 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2026-07-28
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://link-mcp.hultra-site.workers.dev: tools/list returned 5 tools to an anonymous client, including cherche_capacite (write), etat_serveur (write), config_pour (write), changements (write), etat_protocoles (write)

    What this check looks for

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.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http registry-uptime https://link-mcp.hultra-site.workers.dev
claude mcp add --transport http registry-uptime https://link-mcp.hultra-site.workers.dev

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": [],
    "ask": [
      "mcp__registry-uptime__cherche_capacite",
      "mcp__registry-uptime__etat_serveur",
      "mcp__registry-uptime__config_pour",
      "mcp__registry-uptime__changements",
      "mcp__registry-uptime__etat_protocoles"
    ],
    "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 registry-uptime. Review it before you use it.

Capability tags behind 1 rule
  • mcp__registry-uptime__etat_serveur outbound

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/link.hultra/mcp-registry-uptime/verify?hash=10ded8046f91a035726d8104233a68a4d94a0bbbedda67c8ea8648c15e672dc7" | jq -e '.changed == false'

Pinned hash 10ded8046f91, from Nov 18, 2026, 17:18 UTC.

Watch

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

https://radar.anlyon.com/servers/link.hultra/mcp-registry-uptime/changes.xml

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

Badge

Anlyon Radar badge for link.hultra/mcp-registry-uptime
[![Anlyon Radar](https://radar.anlyon.com/badge/link.hultra/mcp-registry-uptime.svg)](https://radar.anlyon.com/servers/link.hultra/mcp-registry-uptime)

Source: MCP Registry. Synced Oct 21, 2026, 18:53 UTC.

mcp-registry-uptime: questions and answers

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

Is the mcp-registry-uptime safe?

No scan can promise that. What its definitions show: 5 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the mcp-registry-uptime delete data?

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

Can the mcp-registry-uptime 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 mcp-registry-uptime have?

5 tools: 5 write. cherche_capacite, etat_serveur, config_pour, changements and etat_protocoles.

Does the mcp-registry-uptime need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the mcp-registry-uptime send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): etat_serveur.

Has the mcp-registry-uptime changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.