Remote MCP · Endpoint

TokenOS Smart Contract Audit MCP server

No. TokenOS Smart Contract Audit answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://tokenos.ai/api/mcp/apps/contract-audit

The last check completed an MCP handshake.

Registry name
ai.tokenos/contract-audit
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
197 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Scan Solidity & Anchor code
Listing
From the official MCP registry (active).
Recent checks of TokenOS Smart Contract Audit
CheckedResultHandshake
1 hour agoHandshake completed197 ms
2 days agoHandshake completed217 ms
5 days agoHandshake completed781 ms
7 days agoHandshake completed251 ms
9 days agoHandshake completed169 ms
11 days agoHandshake completed169 ms
13 days agoHandshake completed125 ms
15 days agoHandshake completed207 ms
17 days agoHandshake completed213 ms
19 days agoHandshake completed402 ms
20 days agoHandshake completed1.11 s
22 days agoHandshake completed418 ms
23 days agoHandshake completed274 ms
25 days agoHandshake completed433 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with TokenOS Smart Contract Audit and makes no claim about it beyond what these checks measured.