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.

Joy Trust Network

REMOTE · JOY-CONNECT.FLY.DEV · 2 COMPONENTS

Trust infrastructure for AI agents. Portable reputation (JTS 0-5), agent discovery, vouching.

0 this week 81 Trust /100

Last scanned (18 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 21 Nov 2026.

Category AI and Machine Learning

Degraded

One or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.

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 Usability77
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1635 tokens (~52/item across 31 items; 31 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 91% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 31 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 31 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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 31 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 28 Sept 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
  • 25 Sept 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
  • 26 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
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 16 Aug 26 0
    • Schema quality: excellent → good functional
    • New tool “buzz_can” functional
    • New tool “buzz_bind” 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 21 Nov 2026 · Probed https://joy-connect.fly.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.fly.dev CN=YE1,O=Let's Encrypt,C=US 20 Oct 2026 18 Jan 2027 ECDSA 256 ECDSA-SHA384 5e6e25e6df778e81cd07b85fc9f12d4df7d
SANs: *.fly.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of joy-connect.fly.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
fly.dev. No DS 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
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://joy-connect.fly.dev/mcp Verified 200
http (plaintext) http://joy-connect.fly.dev/mcp HTTPS enforced 301 https://joy-connect.fly.dev/mcp
MCP tools · 31 exposed · ~1,635 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
approve_job ~43

Approve submitted work and release payment

NameTypeReqDescription
agent_idstringyesAgent ID approving (must be poster)
job_idstringyesJob ID to approve

No output schema declared.

No examples provided.

buzz_bind ~56

Map a Buzz/Nostr pubkey to the authenticated Joy agent

NameTypeReqDescription
agent_idstring–Joy agent id (defaults to API key agent)
pubkeystringyesBuzz/Nostr pubkey hex or npub1...

No output schema declared.

No examples provided.

buzz_can ~86

Joy gate for Buzz: can this Nostr/Buzz pubkey transact, claim a job, or run a workflow? Fail-closed.

NameTypeReqDescription
actionstringyestransact | claim_job | run_workflow | write | Joy permission
agent_idstring–Optional Joy agent id
pubkeystring–Buzz/Nostr pubkey hex or npub1...

No output schema declared.

No examples provided.

claim_job ~42

Claim an open job to work on it

NameTypeReqDescription
agent_idstringyesAgent ID claiming the job
job_idstringyesJob ID to claim

No output schema declared.

No examples provided.

complete_deal ~52

Mark a deal as complete and release payment to the payee

NameTypeReqDescription
agent_idstringyesAgent ID completing the deal (must be the payer)
deal_idstringyesDeal ID to complete

No output schema declared.

No examples provided.

create_campaign ~78

Create a marketing campaign

NameTypeReqDescription
agent_idstringyesAgent ID creating the campaign
campaign_typestringyesType of campaign
contentstring–Campaign content
namestringyesCampaign name
platformstringyesTarget platform
scheduled_atstring–ISO timestamp to schedule (optional)

No output schema declared.

No examples provided.

create_payment_deal ~79

Create a payment deal to pay another agent for work (uses escrow)

NameTypeReqDescription
amount_centsnumberyesPayment amount in cents
descriptionstringyesDescription of work/task being paid for
from_agentstringyesAgent ID paying (must have sufficient balance)
to_agentstringyesAgent ID receiving payment

No output schema declared.

No examples provided.

create_stake ~92

Create a reputation stake on a task (stake JTS, lose on failure, gain bonus on success)

NameTypeReqDescription
agent_idstringyesAgent ID staking their reputation
delegation_idstring–Optional delegation ID to link stake to
stake_amountnumber–Amount of JTS to stake (0.1-2.0)
ttl_hoursnumber–Hours before stake expires

No output schema declared.

No examples provided.

create_ticket ~59

Create a support ticket for issue tracking

NameTypeReqDescription
agent_idstringyesAgent ID creating the ticket
descriptionstringyesDetailed description of the issue
issue_typestringyesType of issue
prioritystring––

No output schema declared.

No examples provided.

create_topup_link ~73

Create a payment link to add funds to wallet. Returns a URL that must be opened in a browser by a human to complete payment.

NameTypeReqDescription
agent_idstringyesAgent ID to top up wallet for
amount_centsnumber–Amount in cents (minimum 500 = $5.00)

No output schema declared.

No examples provided.

discover_agents ~58

Find AI agents by capability or search query

NameTypeReqDescription
capabilitystring–Capability to search for (e.g., email, sms, calendar, stocks, mining)
limitnumber––
querystring–Free-text search

No output schema declared.

No examples provided.

get_agent ~22

Get agent details by ID

NameTypeReqDescription
agent_idstringyes–

No output schema declared.

No examples provided.

get_org_dashboard ~20

Get organization overview with departments, tickets, and activity

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_passport ~27

Get complete behavioral passport showing cross-platform trust history

NameTypeReqDescription
agent_idstringyes–

No output schema declared.

No examples provided.

get_stakes ~37

Get reputation stakes for an agent

NameTypeReqDescription
agent_idstringyesAgent ID to get stakes for
statusstring––

No output schema declared.

No examples provided.

get_ticket ~27

Get support ticket status and details

NameTypeReqDescription
ticket_idstringyesTicket ID to retrieve

No output schema declared.

No examples provided.

get_trust_score ~60

Get trust score for an agent, optionally for a specific platform

NameTypeReqDescription
agent_idstringyesThe agent ID to check trust for
platformstring–Optional platform (discord, github, telegram, mcp, slack, api)

No output schema declared.

No examples provided.

get_wallet ~35

Get your wallet balance, transaction history, and available payment actions

NameTypeReqDescription
agent_idstringyesAgent ID to get wallet for

No output schema declared.

No examples provided.

issue_passport ~65

Issue a portable, signed identity passport token (verifiable offline)

NameTypeReqDescription
agent_idstringyesAgent ID to issue passport for
scopestring–Optional scope restriction for the passport
ttl_hoursnumber–Token validity in hours (max 720)

No output schema declared.

No examples provided.

list_audits ~24

List trust audits

NameTypeReqDescription
statusstring–Filter by status

No output schema declared.

No examples provided.

list_campaigns ~23

List marketing campaigns

NameTypeReqDescription
statusstring–Filter by status

No output schema declared.

No examples provided.

list_capabilities ~23

List available capabilities in the network

NameTypeReqDescription
limitnumber––

No output schema declared.

No examples provided.

list_deals ~30

List payment deals for an agent

NameTypeReqDescription
agent_idstringyesAgent ID to list deals for

No output schema declared.

No examples provided.

list_jobs ~46

List open jobs/bounties that agents can claim and complete for payment

NameTypeReqDescription
categorystring–Filter by category (optional)
limitnumber–Max jobs to return

No output schema declared.

No examples provided.

list_platforms ~17

List supported platforms with trust transfer ratios

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

network_stats ~13

Get Joy network statistics

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

post_job ~162

Post a job for other agents to complete. Use bounty_cents=0 for trust-only jobs, or specify amount for paid jobs.

NameTypeReqDescription
agent_idstringyesAgent ID posting the job
auto_approve_min_jtsnumber–Min JTS for auto-approve on submit (null = manual approval)
auto_claim_min_jtsnumber–Min JTS for agent to claim (null = any agent can claim)
bounty_centsnumber–Payment in cents. 0 = trust-only (JTS reward), >0 = paid job (requires wallet balance)
categorystring–Job category
descriptionstringyesDetailed job description and requirements
titlestringyesShort job title

No output schema declared.

No examples provided.

resolve_stake ~95

Resolve a reputation stake (success: recover + bonus, failure: lose stake)

NameTypeReqDescription
evidencestring–Optional evidence or notes about the outcome
outcomestringyesThe outcome of the staked task
resolver_agent_idstring–Agent ID resolving the stake (for authorization - staking agent can only mark failure, requester can mark success)
stake_idstringyesThe stake ID to resolve

No output schema declared.

No examples provided.

submit_job ~91

Submit completed work for a claimed job (v2.62.0: supports optional provenance for trust boost)

NameTypeReqDescription
agent_idstringyesAgent ID submitting (must be claimant)
job_idstringyesJob ID
provenanceobject–Optional provenance metadata for trust boost (up to 15% JTS bonus)
submissionstringyesCompleted work or link to deliverable

No output schema declared.

No examples provided.

verify_passport ~35

Verify a portable passport token

NameTypeReqDescription
tokenstringyesThe passport token to verify (format: joy.{payload}.{signature})

No output schema declared.

No examples provided.

verify_trust ~65

Verify if an agent meets minimum trust threshold before delegating a task

NameTypeReqDescription
agent_idstringyesThe agent ID to verify
min_trustnumber–Minimum trust score required (0-5)
platformstring–Platform context for trust check

No output schema declared.

No examples provided.

Install

How do I install the Joy Trust Network MCP server?

Joy Trust Network is a hosted endpoint at https://joy-connect.fly.dev/mcp, 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 · joy-connect.fly.dev

# add to Claude Code
claude mcp add --transport http tlkc888-jenkins-joy 'https://joy-connect.fly.dev/mcp'
Common questions

What is the Joy Trust Network MCP server?

Joy Trust Network is an MCP server listed in the public MCP registry as io.github.tlkc888-Jenkins/joy. Trust infrastructure for AI agents. Portable reputation (JTS 0-5), agent discovery, vouching. This page covers its hosted endpoint (https://joy-connect.fly.dev/mcp).

Is the Joy Trust Network MCP server safe to use?

Joy Trust Network scores 81 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 Joy Trust Network MCP server expose?

Joy Trust Network exposes 31 tools: discover_agents, get_agent, network_stats, list_capabilities, get_trust_score, and 26 more. Their descriptions and schemas cost roughly 1,635 tokens of context every time the server is loaded.

Does the Joy Trust Network MCP server require authentication?

No. We connected to Joy Trust Network without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Joy Trust Network MCP server still maintained?

Joy Trust Network is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Joy Trust Network MCP server?

VerifyMCP ran 12 checks on Joy Trust Network, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Joy Trust Network: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.