
GenPark Trie Prefix Keyword Matcher
io.github.alphaparkincPublished by GitHub account alphaparkincv1.0.1Updated Oct 24, 2026
High-performance in-memory Trie and multi-keyword search engine for prompt routing and entity extrac
Overview
A local in-memory Trie and multi-keyword search engine, packaged as a desktop MCP extension, for prompt routing and entity extraction.
- What you can do
- Provides an in-memory Trie and multi-keyword matching engine.
- Supports prompt routing by matching input text against stored keywords.
- Supports entity extraction from text using prefix and multi-keyword matching.
- No tool list, instructions or README are published, so the exact operations exposed to an assistant are not documented.
- When to use it
- Worth considering when you need fast local keyword or prefix matching over text, such as routing prompts to the right handler or pulling known entities out of input, and want it available to an assistant as a local MCP extension.
- Requirements
- Runs as a local process on the user's machine over stdio, installed as an MCP bundle for desktop clients; no authentication, environment variables or headers are declared. Desktop only; not executable on the web.
Installation
In SourceWeft
- Open GenPark Trie Prefix Keyword Matcher in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.0.1LatestOct 24, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.