Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.Hoya25/nctr-mcp-server

REMOTE · YHWCAODOFMBUSJURAWHP.SUPABASE.CO · 2 COMPONENTS · SCANNED SEP 24

NCTR Alliance rewards — search bounties, check earning rates, and discover communities.

0 this week 79 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 498 tokens (~83/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management84
  • Stability check failed: schema churn in the 30 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.Hoya25/nctr-mcp-server server?

io.github.Hoya25/nctr-mcp-server is a hosted endpoint at https://yhwcaodofmbusjurawhp.supabase.co/functions/v1/mcp/rpc, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · yhwcaodofmbusjurawhp.supabase.co

# add to Claude Code
claude mcp add --transport http hoya25-nctr-mcp-server 'https://yhwcaodofmbusjurawhp.supabase.co/functions/v1/mcp/rpc'
// .cursor/mcp.json
{
  "mcpServers": {
    "hoya25-nctr-mcp-server": {
      "url": "https://yhwcaodofmbusjurawhp.supabase.co/functions/v1/mcp/rpc"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "hoya25-nctr-mcp-server": {
      "type": "http",
      "url": "https://yhwcaodofmbusjurawhp.supabase.co/functions/v1/mcp/rpc"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.hoya25-nctr-mcp-server]
url = "https://yhwcaodofmbusjurawhp.supabase.co/functions/v1/mcp/rpc"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hoya25-nctr-mcp-server": {
      "type": "remote",
      "url": "https://yhwcaodofmbusjurawhp.supabase.co/functions/v1/mcp/rpc",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add hoya25-nctr-mcp-server --url 'https://yhwcaodofmbusjurawhp.supabase.co/functions/v1/mcp/rpc' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  hoya25-nctr-mcp-server:
    url: "https://yhwcaodofmbusjurawhp.supabase.co/functions/v1/mcp/rpc"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "hoya25-nctr-mcp-server": {
      "Transport": "http",
      "Url": "https://yhwcaodofmbusjurawhp.supabase.co/functions/v1/mcp/rpc"
    }
  }
}
# add to Vellum
assistant mcp add hoya25-nctr-mcp-server -t streamable-http -u 'https://yhwcaodofmbusjurawhp.supabase.co/functions/v1/mcp/rpc'
// mcp.json
{
  "mcpServers": {
    "hoya25-nctr-mcp-server": {
      "type": "http",
      "url": "https://yhwcaodofmbusjurawhp.supabase.co/functions/v1/mcp/rpc"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Sept 26 −2
    • Stability: pass → fail security
    • A breaking change shipped without a version bump: still 1.0.0 security
    • Tool “get_ecosystem_funding” was removed security
    • Tool “search_bounties” rewrote its description, which is the text the model reads security
    • “search_bounties” reworded the description of “category” cosmetic
  • 26 Aug 26 81
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 10 Aug 26 0
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • Endpoint reachability: not serving MCP → reachable functional
    • Stability: unverified → 0.50 functional
    • MCP protocol: unverified → pass functional
    • Tool coverage: unverified → 100 functional
  • 9 Aug 26 0
    • Endpoint reachability: reachable → not serving MCP security
    • Stability: 0.43 → unverified security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
    • Tool coverage: 100 → unverified functional
    • Capabilities: pass → unverified functional
    • First check of Schema quality: unverified functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 24 Sept 2026 · Probed https://yhwcaodofmbusjurawhp.supabase.co/functions/v1/mcp/rpc

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=supabase.co CN=WE1,O=Google Trust Services,C=US 26 Aug 2026 24 Nov 2026 ECDSA 256 ECDSA-SHA256 7c35296a896c0a6f13f8495266045d45
SANs: supabase.co, *.supabase.co
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of yhwcaodofmbusjurawhp.supabase.co. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
co. present 7786 8 Verified
supabase.co. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://yhwcaodofmbusjurawhp.supabase.co/functions/v1/mcp/rpc Verified 200
http (plaintext) http://yhwcaodofmbusjurawhp.supabase.co/functions/v1/mcp/rpc HTTPS enforced 301 https://yhwcaodofmbusjurawhp.supabase.co/functions/v1/mcp/rpc
MCP tools · 6 exposed · ~498 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_tier_requirements ~82

Check what is needed to reach a specific Crescendo status tier, or see the full progression path. Shows NCTR lock thresholds, multipliers, and perks for each tier.

NameTypeReqDescription
current_balancenumberCurrent NCTR balance to check tier status and progress to next tier
target_tierstringTarget tier to check requirements for

No output schema declared.

No examples provided.

get_active_promotions ~29

Get currently active promotions, limited-time offers, and special earning opportunities in the NCTR program.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_earning_rates ~85

Get NCTR earning rates for a specific Crescendo status tier, or compare all tiers. Shows the multiplier applied to bounty earnings at each tier level. Higher tiers earn more NCTR per bounty.

NameTypeReqDescription
bounty_idstringOptional bounty ID to calculate tier-adjusted earning amount
tierstringSpecific tier to check. Omit to see all tiers.

No output schema declared.

No examples provided.

get_impact_engines ~80

Discover NCTR Impact Engine communities. Impact Engines are passion-based communities within NCTR — each focused on a different lifestyle vertical. Members can join any Impact Engine to connect with like-minded people and access community-specific experiences.

NameTypeReqDescription
categorystringFilter by category (Powersports, Lacrosse, Entertainment, Skilled Trades, Recovery, Wellness)

No output schema declared.

No examples provided.

get_onboarding_link ~60

Generate a link for a new member to join NCTR Alliance. Optionally include a referral code. Returns the sign-up URL and a summary of what new members earn.

NameTypeReqDescription
referral_codestringOptional referral code to credit the referring member

No output schema declared.

No examples provided.

search_bounties ~162

Search and filter available NCTR bounties. Filter by category (entry, shopping, merch, referral, engagement), minimum/maximum NCTR amount, or keyword. Returns bounty details including name, amount, lock period, and requirements. All bounties use 360LOCK — tokens stay yours after the lock period.

NameTypeReqDescription
categorystringFilter by bounty category: entry, shopping, merch, referral, engagement
keywordstringSearch keyword to match against bounty name, description, or tags
max_amountnumberMaximum NCTR amount
min_amountnumberMinimum NCTR amount
repeatable_onlybooleanIf true, only return bounties that can be earned multiple times

No output schema declared.

No examples provided.

Common questions

What is the io.github.Hoya25/nctr-mcp-server server?

io.github.Hoya25/nctr-mcp-server is listed in the public MCP registry as io.github.Hoya25/nctr-mcp-server. NCTR Alliance rewards, search bounties, check earning rates, and discover communities. This page covers its hosted endpoint (https://yhwcaodofmbusjurawhp.supabase.co/functions/v1/mcp/rpc).

Is the io.github.Hoya25/nctr-mcp-server server safe to use?

io.github.Hoya25/nctr-mcp-server scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.Hoya25/nctr-mcp-server server expose?

io.github.Hoya25/nctr-mcp-server exposes 6 tools: search_bounties, get_earning_rates, check_tier_requirements, get_active_promotions, get_onboarding_link, get_impact_engines. Their descriptions and schemas cost roughly 498 tokens of context every time the server is loaded.

Does the io.github.Hoya25/nctr-mcp-server server require authentication?

No. We connected to io.github.Hoya25/nctr-mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.Hoya25/nctr-mcp-server server still maintained?

io.github.Hoya25/nctr-mcp-server is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.