Skip to contentComing soon Social activity in project rankings
Invisible

Tell your agent
about Invisible.

See which NEAR projects people keep using, and give your agent the evidence behind each ranking.

Connect your agent in two steps

Pick a protocol and an environment to see the setup.

Docs
Docs
Docs
Docs

1. Add the server

claude mcp add --transport http invisible https://invisible-gray.vercel.app/api/mcp

2. Ask in chat

Which NEAR projects brought the most signers back? Show me the evidence.

1. Add the server in .cursor/mcp.json

{
  "mcpServers": {
    "invisible": {
      "url": "https://invisible-gray.vercel.app/api/mcp"
    }
  }
}

2. Ask in Agent chat

Which NEAR projects brought the most signers back? Show me the evidence.

1. Add the server in your terminal

codex mcp add invisible --url https://invisible-gray.vercel.app/api/mcp

2. Ask in a new Codex session

Which NEAR projects brought the most signers back? Show me the evidence.

1. Add to MCP Servers → Manage → View Raw Config

{
  "mcpServers": {
    "invisible": {
      "serverUrl": "https://invisible-gray.vercel.app/api/mcp"
    }
  }
}

2. Reload MCP servers and ask in chat

Which NEAR projects brought the most signers back? Show me the evidence.

1. Read the returning signer ranking

curl -fsS 'https://invisible-gray.vercel.app/api/v1/returning-signers?limit=10'

2. Inspect a project

curl -fsS 'https://invisible-gray.vercel.app/api/v1/projects/rhea'

1. Fetch returning signers

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();

2. Read the project evidence

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());

1. Discover the agent

curl -fsS 'https://invisible-gray.vercel.app/.well-known/agent-card.json'

2. Send a research request

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."}]}}}'

1. Discover the agent

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();

2. Send a research request

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());

1. Install in your project

mkdir -p .agents/skills/invisible && curl -fsS 'https://invisible-gray.vercel.app/skill/SKILL.md' -o .agents/skills/invisible/SKILL.md

2. Use the skill in a new session

$invisible Which NEAR projects brought the most signers back? Show me the evidence.

1. Install in your project

mkdir -p .claude/skills/invisible && curl -fsS 'https://invisible-gray.vercel.app/skill/SKILL.md' -o .claude/skills/invisible/SKILL.md

2. Use the skill in chat

/invisible Which NEAR projects brought the most signers back? Show me the evidence.

How rankings work

Follow a NEAR contract call from the activity we count to the score you see.

  1. Mapped NEAR contracts

    Count signing accounts

    Count distinct accounts that directly attempt a function call to a project’s mapped contracts. Count each account once per project in each window.

  2. Two 28-day windows

    Find who came back

    Compare two adjacent 28-day UTC windows. An account that appears in both counts as a returning signer.

  3. 50 signers per window

    Check eligibility

    Require a verified token and at least 50 signers in each window, plus minimums for returning signers, weekly activity, and active days.

  4. Activity score / 100

    Rank eligible projects

    Compare adjusted return rate, returning signer count, adjusted signer growth, and activity spread against eligible peers. Higher scores rank first.

Explore contract evidence

What moves a project up?

Read the methodology
70%

On-Chain Activity

Usage across the project’s attributed contracts.

20%

Pool Reserves

Largest indexed NEAR pool, compared with ranked peers.

10%

Market Cap / FDV

Reported market cap as a share of fully diluted valuation.

Trace the evidence

See what each source contributes and where to check it yourself.

Historical contract activity

Build comparable 28-day signer cohorts from indexed NEAR mainnet function calls.

Check the UTC window and mapped contracts.

NEAR Public Lakehouse

Roadmap

What’s live today and what we plan to build next.

  1. Verify NEAR Activity

    Complete

    Map projects to contracts, compare returning signers, and link each finding to source transactions.

  2. Publish the Research Workspace

    Complete

    Explore activity and investment rankings, inspect vesting evidence, and compare signer forecasts against observed cohorts.

  3. Track Social and Product Activity

    Coming Soon

    Measure activity from official channels and releases alongside on-chain usage, with separate source and coverage labels.

  4. Follow Projects and Unlocks

    Coming Soon

    Save a watchlist and surface changes in retention, upcoming unlocks, and new contract deployments.

  5. Explore an Invisible Token

    Coming Soon

    Publish proposed utility, distribution, and launch criteria before announcing any dates or terms.