_ registry / mcp streamable-http · checked 1h ago

com.splidia/notes

https://mcp.splidia.com

Registry code: e5829b7739ab89e2

api record

Server MCP read-only di SPLIDIA (splidia.com), marchio del gruppo CSIDIA S.r.l.: giunzione e certificazione della fibra ottica, progettazione di reti ottiche, cablaggio di data center, reti industriali, IT e AI applicata alle infrastrutture. Su questo endpoint i tool rispondono per impostazione predefinita sui contenuti e sui servizi di SPLIDIA: usa 'capabilities' per il catalogo dei servizi, 'match_use_case' per capire quale servizio risolve un'esigenza descritta a parole, 'search' e 'fetch' per gli articoli tecnici. Per estendere la risposta all'intero gruppo (inclusa csidia.com: dati, AI e…

endpoint
https://mcp.splidia.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is com.splidia/notes live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is com.splidia/notes free to use?
Yes — the hub reached it with no key and no payment.
What tools does com.splidia/notes have?
4 tools: fetch, capabilities, match_use_case, search.
Is com.splidia/notes safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.2%

90 days 99.2%· all time 99.2%

latency
191ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 364 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
_ what it is for
used for
  • find fiber optic and network services
  • match a need to a company service
  • search technical articles
takes → gives
text → text, data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search reads open 12h ago

    Cerca negli articoli (Note operative) di csidia.com (dati, AI, conformità nei settori critici) e splidia.com (fibra ottica, reti, data center). Ritorna una lista di risultati con id da passare a 'fetch'. / Searches the operational notes of csidia.com and splidia.com. Returns results whose id can be passed to 'fetch'.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "site": {
          "enum": [
            "all",
            "csidia",
            "splidia"
          ],
          "type": "string",
          "description": "Filtro sito (default all)"
        },
        "limit": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1,
          "description": "Numero massimo di risultati (default 8)"
        },
        "query": {
          "type": "string",
          "description": "Termini di ricerca / search terms"
        },
        "language": {
          "enum": [
            "all",
            "it",
            "en"
          ],
          "type": "string",
          "description": "Filtro lingua (default all)"
        }
      }
    }
    arguments 36 lines
  • fetch reads unknown 12h ago

    Ritorna il testo integrale di un articolo dato il suo id (l'URL restituito da 'search'). / Returns the full text of an article given its id (the URL returned by 'search').

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Id/URL dell'articolo"
        }
      }
    }
    arguments 12 lines
  • capabilities reads unknown never probed

    Profilo del gruppo CSIDIA e catalogo dei servizi: chi siamo, posizionamento, capacità (cosa facciamo, risultati, settori, modelli di erogazione, pagina, articoli correlati), settori, vincoli e come iniziare. csidia = dati/AI/conformità, splidia = fibra ottica/reti/data center. / Profile of the CSIDIA group and its service catalogue: positioning, capabilities, sectors, delivery models, constraints and how to start.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "site": {
          "enum": [
            "all",
            "csidia",
            "splidia"
          ],
          "type": "string",
          "description": "Marchio di cui restituire il profilo (default all) / brand to profile"
        },
        "detail": {
          "type": "boolean",
          "description": "false (default) = una riga per capacità, risposta compatta; true = descrizione completa, risultati, domande tipiche e articoli correlati / false (default) = one line per capability; true = full detail"
        },
        "language": {
          "enum": [
            "it",
            "en"
          ],
          "type": "string",
          "description": "Lingua dei testi (default it) / text language"
        },
        "capability_id": {
          "type": "string",
          "description": "Dettaglio di una sola capacità, per id (es. 'conformita-documentale-assistita') / detail for a single capability id"
        }
      }
    }
    arguments 31 lines
  • match_use_case reads unknown never probed

    Data la descrizione libera di un'esigenza operativa, restituisce le capacità del gruppo CSIDIA più pertinenti, con il perché (termini che hanno fatto match), il sito di riferimento, il modello di erogazione, gli articoli correlati e il passo successivo. Se non c'è corrispondenza lo dice e restituisce il profilo sintetico. / Given a free-text operational need, returns the most relevant CSIDIA capabilities with the reason for the match, reference site, delivery model, related articles and next step.

    mcp-tool

    {
      "type": "object",
      "required": [
        "need"
      ],
      "properties": {
        "need": {
          "type": "string",
          "description": "Descrizione libera dell'esigenza o del problema / free-text description of the need"
        },
        "limit": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "Numero massimo di capacità (default 3)"
        },
        "sector": {
          "type": "string",
          "description": "Settore di riferimento, id o nome (es. manufacturing, energy, logistics, public-sector, healthcare, defence, telecomunicazioni, data-center, industria) / sector id or name"
        },
        "language": {
          "enum": [
            "it",
            "en"
          ],
          "type": "string",
          "description": "Lingua dei testi (default it) / text language"
        }
      }
    }
    arguments 30 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id e5829b7739ab89e2.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e5829b7739ab89e2/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/e5829b7739ab89e2/badge.svg)](https://brick.blue/agent/e5829b7739ab89e2?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.