MCP server for advanced web search using Tavily
Astgl Knowledge is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
MCP server with 7 tools for searching, citing, and exploring ASTGL content about MCP servers, local AI, and AI automation — includes tutorials, comparisons, freshness tracking, and rate-limited API access
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user astgl-knowledge-mcp '--' npx -y mcp-astgl-knowledge
# 2 — ask your agent for something these tools do
# register, search_articles, get_answer and 14 more
Astgl Knowledge costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Astgl Knowledge as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user astgl-knowledge-mcp '--' npx -y mcp-astgl-knowledgeReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
17 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Register your email to unlock 500 queries/day (up from 50). Returns an API key to add to your MCP server config.
No parameter schema on file.
Search ASTGL articles about MCP servers, local AI, and AI automation. Returns relevant article sections with source URLs for citation.
No parameter schema on file.
Get a direct answer to a question about MCP servers, local AI, or AI automation from ASTGL
No parameter schema on file.
List all topics covered in the ASTGL knowledge base. Shows article titles, descriptions, URLs, and section headings.
No parameter schema on file.
Get a step-by-step tutorial or guide on a topic from ASTGL
No parameter schema on file.
Compare two topics side-by-side using ASTGL
No parameter schema on file.
Get the most recently added articles from ASTGL
No parameter schema on file.
Auto-generate article topic suggestions from query analytics — surfaces content gaps, low-confidence queries, and trending topics that don
No parameter schema on file.
Add a content idea to the ASTGL idea journal. Use this when you spot a topic gap, get a question you can
No parameter schema on file.
Browse and filter ideas in the ASTGL idea journal by status, priority, or source.
No parameter schema on file.
Export ideas from the idea journal as a formatted markdown document.
No parameter schema on file.
Export a single ASTGL article as a formatted markdown blog post with Q&A, metadata, and related links.
No parameter schema on file.
Generate a roundup blog post combining multiple related ASTGL articles on a topic.
No parameter schema on file.
Compile Q&A pairs from ASTGL articles into a FAQ-style markdown document, optionally filtered by topic.
No parameter schema on file.
Generate a comprehensive JSON snapshot of ASTGL analytics for the dashboard — query trends, content coverage, citation tracking, content gaps, and ecosystem status.
No parameter schema on file.
Find ASTGL articles by metadata — tag, content type (article, tutorial, draft, comparison, guide, newsletter, project), title text, and/or publication date range. This is a structured lookup over the article index (no semantic embedding), so use it for questions like
No parameter schema on file.
List every tag in the ASTGL article index with how many articles carry it. Useful for discovering the available tag vocabulary before calling find_articles.
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Astgl Knowledge or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (17 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| register | no tags | |
| search_articles | no tags | |
| get_answer | no tags | |
| list_topics | no tags | |
| get_tutorial | no tags | |
| compare_topics | no tags | |
| get_latest | no tags | |
| suggest_ideas | no tags | |
| add_idea | no tags | |
| list_ideas | untrusted-input | untrusted-input: keyword "browse" |
| export_ideas | no tags | |
| export_article | no tags | |
| export_topic_roundup | no tags | |
| export_qa_compilation | no tags | |
| generate_dashboard_data | no tags | |
| find_articles | no tags | |
| list_tags | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.3.1. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Astgl Knowledge can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.