Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-grayson-sys-awardopedia": {
"args": [
"-y",
"npm"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Free, searchable interface for U.S. federal contract award data sourced from USASpending.gov.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in legal / search
Web and local search using Brave Search API
Production ready MCP server with real-time search, extract, map & crawl.
Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors
mini cli search engine for your docs, knowledge bases, meeting notes, whatever. Tracking current sota approaches while being all local
MCP Security Weekly
Get CVE alerts and security updates for io.github.grayson-sys/awardopedia and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Free, searchable interface for U.S. federal contract award data sourced from USASpending.gov.
# Clone
git clone https://github.com/openclaw/awardopedia.git
cd awardopedia
# Database
psql -d your_db -f scripts/schema.sql
# API
cd api
cp ../.env.example .env # Edit with your values
npm install
npm run dev # Starts on :3001
# Frontend (separate terminal)
cd web
npm install
npm run dev # Starts on :3000, proxies /api to :3001
See .env.example for all required variables. At minimum for local dev:
DATABASE_URL=postgresql://localhost:5432/awardopedia
JWT_SECRET=any-dev-secret
PORT=3001
awardopedia/
├── api/ # Express API server
│ ├── src/
│ │ ├── db/ # Database connection + queries
│ │ ├── middleware/ # Auth, credits, rate limiting
│ │ ├── routes/ # API route handlers
│ │ └── services/ # Claude AI, Stripe, SendGrid
│ └── Dockerfile
├── web/ # React + Vite frontend
│ ├── src/
│ │ ├── components/ # Reusable UI components
│ │ ├── pages/ # Route pages
│ │ ├── styles/ # CSS tokens, global, components
│ │ └── utils/ # API client, formatters, SEO
│ └── public/
├── scripts/
│ ├── schema.sql # PostgreSQL schema
│ ├── ingest.py # Bulk CSV ingestion
│ └── sync.py # Weekly USASpending API sync
├── docs/
│ ├── api.md # API endpoint reference
│ ├── data-model.md # Database schema docs
│ └── deployment.md # Deployment guide
└── assets/ # Brand logos
All contract data is sourced from USASpending.gov, the official open data source of federal spending information maintained by the U.S. Department of the Treasury as mandated by FFATA.
python3 scripts/ingest.py --file contracts.csvpython3 scripts/sync.py (fetches last 7 days from USASpending API)Proprietary. Data sourced from USASpending.gov (public domain).