swiftsign benchmark report
swiftsign has a benchmark score of 22/100 based on installability, startup reliability, MCP capability discovery, documentation quality, and safety signals.
Benchmark score
22
Docs score
0
Config score
0
Safety score
0
Benchmark status
| Install | unknown |
|---|---|
| Startup | unknown |
| Capability discovery | skipped missing config |
| Last tested | Jul 20, 2026 |
Installability
- gitconfidence: medium
git clone https://github.com/shahdadk/swiftsign.git - npmconfidence: medium
npm install # legacy-peer-deps is pinned in .npmrc (React 19 / Next 16) - npxconfidence: medium
npx prisma generate # writes the Prisma client to src/generated/prisma/ - npxconfidence: medium
npx prisma migrate deploy # apply schema migrations to your dev DB
Capabilities
Tools: 0Resources: 0Prompts: 0
No MCP servers found yet
No tools, resources, or prompts have been discovered yet.
Related pages
Frequently asked questions
What does the swiftsign benchmark score include?
It combines install status, startup status, capability discovery, documentation score, configuration score, and safety score into a 0-100 benchmark_score.
Does MCP Server Finder call swiftsign tools during discovery?
No. Capability discovery lists tools, resources, and prompts when possible, but does not invoke tools or read sensitive resources.
Why are some checks skipped?
Checks are skipped when they cannot be run safely without credentials, local configuration, or non-destructive execution guarantees.
Last updated