google-maps-remote: server now serves 6 tools, entry lists 3
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
Research direction
Read registries/toolhive/servers/google-maps-remote/server.json and find the entry for google-developer-knowledge-remote. Update both entries' tool lists to reflect the tools and descriptions reported in the issue. Done means both entries match the reported server tools; the issue does not name a test or validation command.
Written by the indexing model from the issue text.
Description
registries/toolhive/servers/google-maps-remote/server.json lists 3 tools for https://mapstools.googleapis.com/mcp: search_places, lookup_weather, compute_routes.
A tools/list read of that endpoint today (2026-11-07, unauthenticated, no tool called) returns 6:
compute_routeslookup_weatherresolve_maps_urlsresolve_namessearch_along_routesearch_places
search_along_route appeared between our reads of 27 Oct and 6 Nov, and the same read showed rewritten descriptions for compute_routes and lookup_weather. On 6 Nov https://developerknowledge.googleapis.com/mcp (google-developer-knowledge-remote) also rewrote all 3 of its tool descriptions while keeping the same names.
Suggest refreshing both entries' tool lists.
(Disclosure: I work on CrawlCheck, which re-reads registry servers. The change history for both servers is public at https://crawlcheck.io/mcp/changes.)
- Dominant language
- Go
- Stars
- 26
- Forks
- 104
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 69
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stacklok/toolhive-catalog
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
stacklok/toolhive-catalog#1967 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
stacklok/toolhive-catalog#1929 · 1 comment ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
stacklok/toolhive-catalog#1918 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
stacklok/toolhive-catalog#1909 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
stacklok/toolhive-catalog#1908 ·
Maintainers usually reply within 1 day
All issues in stacklok/toolhive-catalog
Similar issues
-
area/networking kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
siderolabs/talos#14972 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
kubectl wait outputs cryptic "error: unrecognized condition: []" when --for is omittedPossibly taken @muskan-creates352 claimed this today. Openkind/bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
kubernetes/kubectl#1910 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
unbound-force/gaze#353 ·
Maintainers usually reply within 1 day
-
bug cross-seed ready-for-human
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day