Skip to content

MCP servers › io.github.agteo › goyondo

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.agteo/goyondo

Trip planner your AI assistant can plan and edit: persistent trips, group plans, booking records. — the publisher's description

3 of 6 record checks metRead-only · tools listed 2026-10-23Topic: productivity-and-docs · AI-classifiedPricing: freemium · AI-classifiedversion 0.2.0MITstandard input/output, streamable HTTP38 tools

Summary

io.github.agteo/goyondo is a remote and local MCP server listed in the official MCP registry at version 0.2.0. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 38 tools, 0 resources and 0 prompts.

Record checks

3 of 6 record checks met · 3 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • met: Package names its licence with a standard (SPDX) identifier
  • met: The version the registry lists can be installed and is not withdrawn
  • not met: npm package carries build provenance (attestation)
  • not met: No known critical or high advisory in the package or its dependencies
  • #7,035 of 15,112 packages by monthly downloads, tied with 11 others
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs
remote and local package
Transport
standard input/output, streamable HTTP
Package
npm · listed version current
License
MIT
Dependencies
0 critical, 2 high advisories
Tools
38
Described as changing data
21 of 38 toolsAI-classified
Mainly works on
accounts and data in outside web servicesAI-classified
Topic
productivity-and-docsAI-classified
Pricing
freemiumAI-classified
Last tested
2026-10-23

Add to your client

Worth knowing before you connect it

  • 21 tools are described as changing something (connect_goyondo, create_trip, update_trip, …): our AI model's reading of the descriptions, not something we tested. We did not call them.
  • 0 critical and 2 high advisories in its dependencies (as resolved on 2026-10-23).

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-23
Mode
read-only (no tool calls)
Latest version
0.2.0, published 2026-10-17 (registry, as of the 2026-10-23 snapshot)
First listed version
2026-10-11 (earliest version still in the registry; older removed versions would be earlier)
Version history
2 versions listed, 2026-10-11 to 2026-10-17; 2 in the 90 days before the 2026-10-23 snapshot.
Most recent 2 versions
  • 0.2.0 · 2026-10-17
  • 0.1.0 · 2026-10-11
(versions still listed in the registry only)
Registry data
snapshot 2026-10-23
Package and repository
checked 2026-10-23
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.2.0 (published 2026-10-17).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory
38tools
0resources
0prompts

What it mainly works on, as our AI model read its tool descriptions: accounts and data in outside web services.

21 of 38 tools are described as changing something (creating, editing, deleting, sending or running).

  • connect_goyondodescribed as changing data

    “Connect this assistant to the user's Goyondo account, or check the connection.”

    Takes no inputs.

  • describe_capabilitieson 2 other serversreads or searches

    “Describe available Goyondo agent capabilities, including input schemas, enum values, and supported interfaces.”

    2 inputs
    • capabilitystring“Optional capability name to describe.”
    • namestring“Alias for capability.”
  • get_schemaon 32 other serversreads or searches

    “Return the JSON input schema for one Goyondo capability, or all schemas if no capability is provided.”

    2 inputs
    • capabilitystring“Optional capability name to fetch schema for.”
    • namestring“Alias for capability.”
  • list_tripson 4 other serversreads or searches

    “List trips for the authenticated user.”

    1 input
    • limitinteger“Maximum number of trips to return.”
  • get_tripon 4 other serversreads or searches

    “Get a single trip by id including full itinerary (days and activities).”

    1 input, 1 required
    • trip_idstringrequired“UUID of the trip”
  • create_tripon 1 other servercreates or changes datadescribed as changing data

    “Create a new trip and optionally generate an AI itinerary.”

    14 inputs, 3 required
    • destinationstringrequired
    • start_datestringrequired“ISO date YYYY-MM-DD”
    • end_datestringrequired“ISO date YYYY-MM-DD”
    • timezonestring“Traveler IANA time zone, e.g.”
    • travelersinteger
    • interestsarray
    • travel_stylestring
    • accommodation_typestring
    • skip_ai_generationboolean“true creates the trip with empty days; fill them with save_itinerary.”
    • originobject“Where this trip starts, if the user told you.”
    • arrival_timestring“Local time the traveller lands on Day 1, HH:MM (24h).”
    • departure_timestring“Local time the traveller leaves on the last day, HH:MM (24h).”
    • groupTripCodestring“Collaborative group trip code.”
    • regeneration_modestring“Required when the group already has a linked itinerary.”
  • update_tripcreates or changes datadescribed as changing data

    “Update trip metadata such as dates, title, traveler count, budget, or status.”

    17 inputs, 1 required
    • trip_idstringrequired“UUID of the trip”
    • titlestring“Trip title, max 255 chars”
    • destinationstring“Destination name”
    • start_datestring“Start date in ISO format YYYY-MM-DD”
    • end_datestring“End date in ISO format YYYY-MM-DD.”
    • travelersinteger“Number of travelers (1–20)”
    • budget_per_personnumber“Budget per person”
    • total_budgetnumber“Total budget”
    • currencystring“3-letter currency code, e.g.”
    • travel_stylestring
    • accommodation_typestring
    • statusstring
    • notesstring“Free-text notes, max 2000 chars”
    • originobject“Where this trip starts.”
    • clear_originboolean“true removes the trip's origin.”
    • arrival_timestring“Local time the traveller lands on Day 1, HH:MM (24h).”
    • departure_timestring“Local time the traveller leaves on the last day, HH:MM (24h).”
  • regenerate_itinerarycreates or changes datadescribed as changing data

    “Regenerate the AI itinerary for an existing trip.”

    1 input, 1 required
    • trip_idstringrequired“UUID of the trip”
  • add_activityon 2 other serverscreates or changes datadescribed as changing data

    “Add an activity to a trip.”

    15 inputs, 2 required
    • trip_idstringrequired“UUID of the trip (from list_trips or get_trip)”
    • titlestringrequired“Activity name, max 255 chars”
    • descriptionstring“Optional details, max 1000 chars”
    • activity_typestring“Canonical enum.”
    • start_timestring“Time in HH:MM 24-hour format.”
    • end_timestring“Time in HH:MM 24-hour format.”
    • duration_minutesinteger“Duration in minutes”
    • locationstring“Venue or area name, max 255 chars”
    • addressstring“Full address, max 500 chars”
    • estimated_costnumber“Cost per person in trip currency”
    • priorityinteger“1 (lowest) to 10 (highest), default 5”
    • notesstring“Internal notes, max 1000 chars”
    • itinerary_idstring“UUID of the itinerary day (from get_trip itinerary[].id).”
    • day_numberinteger“Day of the trip (1 = first day).”
    • datestring“Calendar date YYYY-MM-DD.”
  • update_activityon 4 other serverscreates or changes datadescribed as changing data

    “Update an existing activity.”

    15 inputs, 2 required
    • trip_idstringrequired“UUID of the trip”
    • activity_idstringrequired“UUID of the activity (from get_trip itinerary)”
    • titlestring
    • descriptionstring
    • activity_typestring“Canonical enum.”
    • start_timestring“HH:MM 24-hour format.”
    • end_timestring“HH:MM 24-hour format.”
    • duration_minutesinteger
    • locationstring
    • addressstring
    • estimated_costnumber
    • priorityinteger
    • notesstring
    • day_numberinteger“Move the activity to a different trip day (1 = first day).”
    • datestring“Move the activity to a specific calendar date YYYY-MM-DD.”
  • save_itineraryon 1 other servercreates or changes datadescribed as changing data

    “Save an itinerary you wrote to an existing trip in one call: every day and its activities.”

    2 inputs, 2 required
    • trip_idstringrequired“UUID of the trip”
    • daysarrayrequired“Days to fill.”
  • list_activitieson 12 other serversreads or searches

    “List all activities for a trip as a flat array.”

    1 input, 1 required
    • trip_idstringrequired“UUID of the trip”
Show 26 more tools
  • get_trip_alertsreads or searches

    “Check a trip's plan and return its alerts: venues closed or outside opening hours, public holidays, too much travel or backtracking, duplicates, time overlaps and pace.”

    2 inputs, 1 required
    • trip_idstringrequired“UUID of the trip”
    • modestring“Travel mode for travel-time checks.”
  • delete_activityon 7 other serversdeletesdescribed as changing data

    “Delete an activity from a trip.”

    2 inputs, 2 required
    • trip_idstringrequired
    • activity_idstringrequired
  • get_user_preferenceson 2 other serversreads or searches

    “Get the authenticated user's travel preferences (interests, dietary, accessibility, etc.).”

    Takes no inputs.

  • list_itinerary_segmentsreads or searches

    “List business traveler segments for a trip (flights, hotels, car rentals, meetings).”

    1 input, 1 required
    • trip_idstringrequired“UUID of the trip”
  • get_trip_documentreads or searches

    “Get a trip document by id or search by name (e.g.”

    3 inputs, 1 required
    • trip_idstringrequired“UUID of the trip”
    • document_idstring“UUID of the document (optional if name provided)”
    • namestring“Search by name substring (optional)”
  • get_trip_expense_summaryreads or searches

    “Get expense summary for a trip (for expense report export).”

    1 input, 1 required
    • trip_idstringrequired“UUID of the trip”
  • submit_group_preferencescreates or changes datadescribed as changing data

    “Submit group trip preferences for alignment (Group Harmony).”

    2 inputs, 2 required
    • trip_codestringrequired“Group trip code (e.g.”
    • preferencesobjectrequired“Canonical preference object — see capability description for the full shape and example.”
  • submit_group_inspirationcreates or changes datadescribed as changing data

    “Submit a link, raw text, or explicit place to a group inspiration board.”

    4 inputs, 1 required
    • trip_codestringrequired“Group trip code”
    • urlstring“URL to ingest into the board”
    • textstring“Raw note/text to ingest into the board (max 5000 chars)”
    • placeobject“Explicit place candidate to add.”
  • get_group_boardreads or searches

    “Get the collaborative inspiration board for a group trip, including candidates, reactions, review lane, and readiness signals.”

    1 input, 1 required
    • trip_codestringrequired“Group trip code”
  • react_to_placecreates or changes datadescribed as changing data

    “Vote on a place candidate in a group inspiration board.”

    5 inputs, 3 required
    • trip_codestringrequired“Group trip code”
    • candidate_idstringrequired“Place candidate UUID”
    • votestringrequired“One of "in", "unsure", "out".”
    • starredboolean
    • reasonstring“Required (non-empty) when vote is "out"; the request is rejected with a 400 otherwise.”
  • update_place_candidatecreates or changes datadescribed as changing data

    “Confirm, edit, or ignore a review-lane place candidate on a group inspiration board.”

    8 inputs, 3 required
    • trip_codestringrequired“Group trip code”
    • candidate_idstringrequired“Place candidate UUID”
    • actionstringrequired“"confirm" accepts the candidate as-is (binding when done by a human), "edit" accepts it with the field overrides below, "ignore" drops it from the review lane.”
    • namestring“Applies to action="edit".”
    • citystring“Applies to action="edit".”
    • neighborhoodstring“Applies to action="edit".”
    • categorystring“Applies to action="edit".”
    • blurbstring“Applies to action="edit".”
  • update_user_preferenceson 2 other serverscreates or changes datadescribed as changing data

    “Update the authenticated user's travel preferences.”

    8 inputs
    • interestsarray
    • travel_stylestring
    • accommodation_typestring
    • budget_rangestring
    • preferred_destinationsarray
    • dietary_restrictionsarray
    • accessibility_needsarray
    • home_baseobject“The user's home city.”
  • create_group_tripcreates or changes datadescribed as changing data

    “Create a new group trip.”

    5 inputs
    • titlestring“Group trip name, max 255 chars”
    • tentative_datesobject“Object with start/end date ranges under consideration, e.g.”
    • destination_optionsarray“Array of candidate destination name STRINGS, e.g.”
    • budget_minnumber“Lower bound of the group budget per person”
    • budget_maxnumber“Upper bound of the group budget per person”
  • list_group_tripsreads or searches

    “List all group trips the authenticated user belongs to.”

    Takes no inputs.

  • delete_group_tripdeletesdescribed as changing data

    “Delete a group trip and its members, preferences, and alignment data.”

    1 input, 1 required
    • trip_codestringrequired“Group trip code”
  • join_group_tripcreates or changes datadescribed as changing data

    “Join an existing group trip using its trip_code.”

    1 input, 1 required
    • trip_codestringrequired“Group trip code from the share link”
  • get_group_tripreads or searches

    “Get a group trip by its trip_code, including members and current preferences.”

    1 input, 1 required
    • trip_codestringrequired“Group trip code”
  • run_alignmentruns code or commandsdescribed as changing data

    “Trigger Group Harmony alignment — AI reconciles all member preferences (only dates, destination, and budget are reconciled) and produces a consensus plan.”

    1 input, 1 required
    • trip_codestringrequired“Group trip code”
  • get_alignmentreads or searches

    “Get the latest Group Harmony alignment result for a group trip: consensus_items, conflicts, proposed_destination, proposed_dates, round_number, response_deadline (48h per round), and alignment_score …”

    1 input, 1 required
    • trip_codestringrequired“Group trip code”
  • list_proposalson 15 other serversreads or searches

    “List pending change proposals for a trip (editors and owners only).”

    1 input, 1 required
    • trip_idstringrequired“UUID of the trip”
  • approve_proposalon 3 other serverscreates or changes datadescribed as changing data

    “Approve a pending change proposal on a trip.”

    2 inputs, 2 required
    • trip_idstringrequired“UUID of the trip”
    • proposal_idstringrequired“UUID of the proposal”
  • reject_proposalon 1 other serverdeletesdescribed as changing data

    “Reject a pending change proposal on a trip.”

    2 inputs, 2 required
    • trip_idstringrequired“UUID of the trip”
    • proposal_idstringrequired“UUID of the proposal”
  • get_edit_logreads or searches

    “Get the edit history for a trip, including agent and human changes.”

    1 input, 1 required
    • trip_idstringrequired“UUID of the trip”
  • set_user_preferencecreates or changes datadescribed as changing data

    “Record a travel preference on behalf of the authenticated user.”

    3 inputs, 2 required
    • typestringrequired“Preference category, e.g.”
    • valuerequired“The preference value (string, number, or boolean)”
    • confidencenumber“0.0–1.0.”
  • get_preference_profilereads or searches

    “Get the authenticated user's AI-rendered travel preference profile (full markdown doc).”

    Takes no inputs.

  • update_day_notescreates or changes datadescribed as changing data

    “Set or replace the notes for a specific itinerary day.”

    4 inputs, 2 required
    • trip_idstringrequired“UUID of the trip”
    • day_idstring“UUID of the itinerary day (itinerary.days[n].id from get_trip).”
    • day_numberinteger“Day of the trip (1 = first day).”
    • notesstringrequired“Free-text notes for the day.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does
100% of 38 tools
Says what it returns
63% of 38 tools
States limits, defaults or errors
5% of 38 tools
Says when to use it
13% of 38 tools
Items covered per tool
1.8 of 4 on average

Counted from the listing

Parameters with a description
80% of 131
Tools with a description
100% of 38
Typical description length
223 characters

The tool set

Counted from the listing

Tools
38
Size of the list
about 7,151 tokens for an agent to load (characters ÷ 4)
Naming
38 of 38 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 38 of 38 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the npm package goyondo-mcp

Our sandbox started this package on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
  "mcpServers": {
    "goyondo": {
      "command": "npx",
      "args": [
        "-y",
        "goyondo-mcp@0.1.0"
      ]
    }
  }
}
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "goyondo": {
      "command": "npx",
      "args": [
        "-y",
        "goyondo-mcp@0.1.0"
      ]
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "goyondo": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "goyondo-mcp@0.1.0"
      ]
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"goyondo","type":"stdio","command":"npx","args":["-y","goyondo-mcp@0.1.0"]}'
Claude Code
claude mcp add --transport stdio goyondo -- npx -y goyondo-mcp@0.1.0
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- npx -y goyondo-mcp@0.1.0
  • Optional settings the entry also lists (left out above): GOYONDO_API_KEY.
  • This runs the publisher's code on your machine (npx). Read its README first.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

From the remote endpoint (Streamable HTTP)

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://goyondo.run/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "goyondo": {
      "url": "https://goyondo.run/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "goyondo": {
      "type": "http",
      "url": "https://goyondo.run/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"goyondo","type":"http","url":"https://goyondo.run/mcp"}'
Claude Code
claude mcp add --transport http goyondo https://goyondo.run/mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://goyondo.run/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists
0.1.0
Latest stable
0.1.0
Status
current
Withdrawn
no

Source: registry.npmjs.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

critical0high2moderate0low0

Counted in the full dependency tree as resolved on 2026-10-23 (npm audit). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity
sha512-RxavEnYwmDDWZcBkj…
Signature
signed
License
MIT

Source: the package registry · 2026-10-23.

Usage

Downloads
346 in the last month

Source: api.npmjs.org · 2026-10-23.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint goyondo.run/mcpEndpoint answered and asked for sign-inmatchesour test · 2026-10-23
No credential declared as requiredRequired sign-indiffersour test · 2026-10-23
Published package can be startedStarted and answeredmatchesour test · 2026-10-23
Version 0.1.0 on npmExists and can be installedmatchesnpm · 2026-10-23

Choosing

Record checks

Public records · not a safety rating

3 of 6 record checks met · 3 do not apply

  • #7,035 of 15,112 packages by monthly downloads, tied with 11 others
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • MetPackage names its licence with a standard (SPDX) identifierMIT
  • MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
  • Not metnpm package carries build provenance (attestation)Signed by npm, but no build attestation.
  • Not metNo known critical or high advisory in the package or its dependencies2 critical or high advisories in its dependencies.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.agteo/goyondo

Answered from the data above

Is io.github.agteo/goyondo safe to install?

We do not rate servers as safe or unsafe. 3 of its 6 applicable record checks are met (facts from public records, each listed on this page). What the records show: The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has advisories (2 high; npm audit). 21 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Is io.github.agteo/goyondo free to use?

Its website (goyondo.run/) describes a freemium pricing model. This is an AI-classified reading of the page on 2026-10-23, so check the page itself before relying on it.

Has io.github.agteo/goyondo been security tested?

Partly. 2 of the 12 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

What can io.github.agteo/goyondo do?

It lists 38 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, delete and run code or commands. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.agteo/goyondo change or delete data?

21 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Is the listed version current?

Yes. The registry lists 0.1.0, the latest stable release on npm.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

Active servers whose topic is also “productivity-and-docs” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not applicable
  17. Consent handling: not applicable
  18. Sign-in metadata: not applicable

2 exercised10 not run (reason given)6 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 12 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 10
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
Does not apply to this server · 6
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model. This server also has a remote test (1 of 18 applicable checks exercised).

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted the published package in an isolated sandbox (read-only mode)
  2. 5,779 msConnected after 0 redirects.
  3. Read the inventory: 38 tools, 0 resources, 0 prompts.
  4. 7,477 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
AI-classified · 2026-10-23
Pricing modelAI-classified
freemium
read from goyondo.run/ · 2026-10-23

“The free plan includes 3 active Goyondo AI-planned trips, with bonus AI trip slots available by sharing.”

Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-10-23
MCP capability
tools
our test · 2026-10-23
Transport
standard input/output, streamable HTTP
registry · 2026-10-23
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
registry · 2026-10-23
Freshness
0–30 days
registry updatedAt · 2026-10-23
Lifecycle status
registry · 2026-10-23
License class
package registry · 2026-10-23
Integrity hash
declared (sri)
package registry · 2026-10-23
Signature / provenance
signed
package registry · 2026-10-23
Dependency advisories
high
npm audit · 2026-10-23
Popularity
346 downloads a month
package registry · 2026-10-23
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
either (remote or your machine)
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.agteo/goyondo: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.agteo/goyondo

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 3 of 6 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.agteo/goyondo)](https://protocolprobe.com/mcp/servers/io.github.agteo/goyondo)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology