MCP server health, State of MCP census

Syenite

io.github.syenite-ai/syenite

DeFi interface for AI agents: swap, bridge, yield, lending. Live at syenite.ai.

healthy checked 2026-07-02 · 7/8 checks passed · keyless

Checks

The exact rows akashi check io.github.syenite-ai/syenite prints, from the 2026-07-02 census.

CheckStatusDetail
registry statuspassactive
server.json validpassvalidates against its declared JSON Schema
repo reachablewarnprobe error: http2: response body closed
package npmpasspublished (0.5.0)
remote reachablepassHTTP 200 via initialize
MCP conformancepassinitialize handshake ok
tools/listpass46 tools: syenite.help, lending.rates.query, lending.market.overview, lending.position.monitor, lending.risk.assess, yield.opportunities, yield.assess, swap.quote, ...
at least one live entrypointpass2 alive

Evidence

Repository

github · error

https://github.com/syenite-ai/syenite

Packages

  • npm @syenite/mcp · published(0.5.0)

Remote endpoints

  • https://syenite.ai/mcp

    streamable-http · reachable· HTTP 200· initialize_ok

    46 tools: syenite.help, lending.rates.query, lending.market.overview, lending.position.monitor, lending.risk.assess, yield.opportunities, yield.assess, swap.quote, ...

server.json

validagainst its declared schema

One of 14559 servers in the 2026-07-02 State of MCP census: 11582 healthy (79.6%), 2212 degraded (15.2%), 596 dead (4.1%), 169 unknown (1.2%).

Verify it yourself

This page is a static read of one dated probe. Run the same check locally, any time, with no key:

$ akashi check io.github.syenite-ai/syenite

Install Akashi - single Go binary, zero keys, MIT licensed.

Is this your server?

Claiming a server (an auto-refreshing badge and a verified publisher profile) is coming soon. Until then, embed the verified-on-date badge yourself with akashi check io.github.syenite-ai/syenite --badge.

Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.