mcp-registry/io.github.syenite-ai/syenite · v0.6.3
Also listed as glama/syenite-ai/syenite
As of 2026-10-11 20:45 UTC, the Syenite Ai Syenite MCP server is unknown. Over the last 30 days it answered 0% of Glimind's liveness checks.
DeFi interface for AI agents: swap, bridge, yield, lending. Live at syenite.ai.
Point your MCP client at this streamable-http endpoint: https://syenite.ai/mcp
The endpoint did not complete an MCP handshake.
Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →
46 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
46 tool name(s) contain "." or exceed 64 characters, which OpenAI-compatible function calling rejects (^[a-zA-Z0-9_-]{1,64}$).
Use "_" or "-" instead of "." and keep names to 64 characters, so clients built on OpenAI-style tool calling don't have to rename (or drop) them. How to fix →
3 parameter(s) across 2 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.syenite-ai%2Fsyenite/fixes
{
"name": "alerts_check",
"description": "Triggers an immediate evaluation of all registered watches and returns any unacknowledged alerts grouped by severity (critical or warning). Call this to poll for fired conditions without waiting for a webhook — it is safe to call repeatedly and will re-evaluate all watches on each call. Optionally pass watchId to filter results to a single watch; pass acknowledge: true with a watchId to clear that watch's alerts after reading. Returns alert count, severity breakdown, and per-alert details includ",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"watchId": {
"type": "string",
"description": "Filter alerts for a specific watch ID"
},
"acknowledge": {
"type": "boolean",
"default": false,
"description": "Mark returned alerts as acknowledged"
}
}
},
"annotations": {
"title": "Check Alerts",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}{
"name": "alerts_list",
"description": "Returns all currently registered watches with their full configuration, type (lending, rate, carry, yield, prediction), threshold parameters, and last check timestamp. Use this to audit active monitors before creating new ones or to retrieve watch IDs needed for alerts.remove. Takes no parameters and never triggers a live check — for current alert state, call alerts.check instead.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"title": "List Watches",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}{
"name": "alerts_remove",
"description": "Removes a registered watch by its ID, stopping all monitoring and alert generation for that watch immediately and permanently. Requires the watchId returned when the watch was created (or retrieved via alerts.list). Returns success: true if the watch was found and removed, or false if the ID was not found. Does not affect other watches or their accumulated alerts.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"watchId"
],
"properties": {
"watchId": {
"type": "string",
"description": "ID of the watch to remove"
}
}
},
"annotations": {
"title": "Remove Watch",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.syenite-ai/syenite"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.syenite-ai/syenite"}) over MCP.
alerts.watch ~865 tokensrates.watch ~637 tokensprediction.watch ~543 tokensswap.quote ~521 tokenstx.guard ~514 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.syenite-ai%2Fsyenite?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.syenite-ai%2Fsyenite?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.syenite-ai%2Fsyenite.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.syenite-ai%2Fsyenite.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.syenite-ai%2Fsyenite?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:add809044022ac85…, first seen 2026-10-17, included at leaf 12410 of 40,064. Version history · verify what your client received.
Compare: most reliable security servers · most reliable other servers · most reliable finance servers · most reliable search servers · most reliable data servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-11 20:45 UTC, the Syenite Ai Syenite MCP server is unknown. Over the last 30 days it answered 0% of Glimind's liveness checks.
Syenite Ai Syenite MCP server advertises 46 tools, including alerts.check, alerts.list, alerts.remove, alerts.watch, find.strategy.
Point your MCP client at this streamable-http endpoint: https://syenite.ai/mcp
Glimind scanned all 46 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.