On-Chain Activity
Usage across the project’s attributed contracts.
See which NEAR projects people keep using, and give your agent the evidence behind each ranking.
Pick a protocol and an environment to see the setup.
claude mcp add --transport http invisible https://invisible-gray.vercel.app/api/mcpWhich NEAR projects brought the most signers back? Show me the evidence.{
"mcpServers": {
"invisible": {
"url": "https://invisible-gray.vercel.app/api/mcp"
}
}
}Which NEAR projects brought the most signers back? Show me the evidence.codex mcp add invisible --url https://invisible-gray.vercel.app/api/mcpWhich NEAR projects brought the most signers back? Show me the evidence.{
"mcpServers": {
"invisible": {
"serverUrl": "https://invisible-gray.vercel.app/api/mcp"
}
}
}Which NEAR projects brought the most signers back? Show me the evidence.curl -fsS 'https://invisible-gray.vercel.app/api/v1/returning-signers?limit=10'curl -fsS 'https://invisible-gray.vercel.app/api/v1/projects/rhea'const response = await fetch("https://invisible-gray.vercel.app/api/v1/returning-signers?limit=10");
if (!response.ok) throw new Error(response.statusText);
const ranking = await response.json();const evidence = await fetch("https://invisible-gray.vercel.app/api/v1/projects/rhea");
if (!evidence.ok) throw new Error(evidence.statusText);
console.log(await evidence.json());curl -fsS 'https://invisible-gray.vercel.app/.well-known/agent-card.json'curl -fsS 'https://invisible-gray.vercel.app/api/a2a' \
-H 'Content-Type: application/json' \
--data '{"jsonrpc":"2.0","id":1,"method":"message/send","params":{"message":{"kind":"message","role":"user","messageId":"invisible-example-1","parts":[{"kind":"text","text":"Which NEAR projects brought the most signers back? Show me the evidence."}]}}}'const discovery = await fetch("https://invisible-gray.vercel.app/.well-known/agent-card.json");
if (!discovery.ok) throw new Error(discovery.statusText);
const agent = await discovery.json();const response = await fetch(agent.url, {
method: "POST",
headers: {"Content-Type": "application/json"},
body: JSON.stringify({
"jsonrpc": "2.0",
"id": 1,
"method": "message/send",
"params": {
"message": {
"kind": "message",
"role": "user",
"messageId": "invisible-example-1",
"parts": [
{
"kind": "text",
"text": "Which NEAR projects brought the most signers back? Show me the evidence."
}
]
}
}
})
});
if (!response.ok) throw new Error(response.statusText);
console.log(await response.json());mkdir -p .agents/skills/invisible && curl -fsS 'https://invisible-gray.vercel.app/skill/SKILL.md' -o .agents/skills/invisible/SKILL.md$invisible Which NEAR projects brought the most signers back? Show me the evidence.mkdir -p .claude/skills/invisible && curl -fsS 'https://invisible-gray.vercel.app/skill/SKILL.md' -o .claude/skills/invisible/SKILL.md/invisible Which NEAR projects brought the most signers back? Show me the evidence.Follow a NEAR contract call from the activity we count to the score you see.
Count distinct accounts that directly attempt a function call to a project’s mapped contracts. Count each account once per project in each window.
Compare two adjacent 28-day UTC windows. An account that appears in both counts as a returning signer.
Require a verified token and at least 50 signers in each window, plus minimums for returning signers, weekly activity, and active days.
Compare adjusted return rate, returning signer count, adjusted signer growth, and activity spread against eligible peers. Higher scores rank first.
Usage across the project’s attributed contracts.
Largest indexed NEAR pool, compared with ranked peers.
Reported market cap as a share of fully diluted valuation.
See what each source contributes and where to check it yourself.
Build comparable 28-day signer cohorts from indexed NEAR mainnet function calls.
Check the UTC window and mapped contracts.
NEAR Public LakehouseWhat’s live today and what we plan to build next.
Map projects to contracts, compare returning signers, and link each finding to source transactions.
Explore activity and investment rankings, inspect vesting evidence, and compare signer forecasts against observed cohorts.
Measure activity from official channels and releases alongside on-chain usage, with separate source and coverage labels.
Save a watchlist and surface changes in retention, upcoming unlocks, and new contract deployments.
Publish proposed utility, distribution, and launch criteria before announcing any dates or terms.