Skip to main content
Glama
524,660 tools. Updated 2026-09-06 17:35

"Handshake" matching MCP tools:

  • Terminate an active handshake by providing the handshake ID and reason for revocation. Only parties to the handshake can revoke, and the action cannot be undone.
    Apache 2.0
    Destructive
  • Fetch full details of a Handshake job posting, including description, requirements, salary, deadline, and application method.
    MIT
  • Retrieve your Handshake student profile including name, school, major, graduation year, and account status.
    MIT
  • Bookmark a job posting to your Handshake saved-jobs list by providing the job's posting ID.
    MIT

Matching MCP Servers

Matching MCP Connectors

  • Search for companies and employers on Handshake using name or industry keywords. Specify page and results per page for paginated results.
    MIT
  • Check if any x402 endpoint is ready for autonomous AI agents by validating 9 signals, including payment headers and handshake. Get a 0-100% readiness score with per-check PASS/FAIL details before paying.
    MIT
  • Appends identity claims to an active handshake for policy-based evaluation. Supports full, selective, or zero-knowledge disclosure modes.
    Apache 2.0
  • Look up worked examples for edge-case protocol flows on demand. Get step-by-step guidance for MCP handshake, capability confirmation, and advanced fields.
    MIT
  • Check trust status with a peer or specialist before sending messages, preventing failed transmissions due to missing bilateral trust.
    Apache 2.0
  • Fetch the full body of a known resource URI in one call, avoiding the two-step list-and-read handshake. Get URI, name, description, and content directly for rules, guidelines, or context documents.
    MIT
  • Evaluates handshake presentations against governing policy to determine acceptance, rejection, or pending status, providing reason codes for each outcome.
    Apache 2.0
  • Purchase a content license via Stripe, selecting republication, training, or inference rights. Receive a license key and certificate.
    MIT
  • Approve pending inbound handshakes by specifying the target peer hostname, node_id, or address. Use only when the user has explicitly delegated trust decisions.
    Apache 2.0
  • List inbound handshake requests pending your approval. Review connection requests from human-operated peers, then accept or reject them.
    Apache 2.0
  • Retrieve TLS handshake error statistics from OpenSIPS, calculate error percentages relative to total attempts, and assess severity levels (ok, elevated, high, critical).
    Apache 2.0
  • Retrieve the full state of a handshake to check progress or review completed exchanges, including parties, presentations, binding, and result.
    Apache 2.0
  • Establish mutual trust with a peer or specialist agent. Specialists auto-approve; human peers require explicit approval, enabling secure communication.
    Apache 2.0