Is IBKR Portfolio Builder safe to use?

IBKR Portfolio Builder has an HVTrust score of 33.1/100 (Grade D), ranked #1315 of 1378 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for IBKR Portfolio Builder?

IBKR Portfolio Builder scores 33.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 19 GitHub stars and is categorized under MCP Servers.

IBKR Portfolio Builder

Repository

Remote MCP server for top-down portfolio construction with Interactive Brokers typed catalog of 468 IBKR screeners tagged by strategy intent (value/growth/income/momentum/quality), news, live account access. OAuth + static bearer auth. Works with Claude.ai custom connectors, Claude Code, and any…

MCP Servers Python Listed MIT

Is IBKR Portfolio Builder safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 2.1 / 10

Provenance None

Signed commits 38%

Last push 131d ago

Compare IBKR Portfolio Builder

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: IBKR Portfolio Builder scores 33.1/100 (Grade D), ranked #1315 of 1378 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.1/10; 38% of recent commits are signed; last pushed 2026-06-08. Every point is earned from checkable signals — never paid placement. How scoring works →

How IBKR Portfolio Builder could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Raise the OSSF Scorecard from 2.1 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 0, Dangerous-Workflow 0 +14.4 → 47.5 D · #607 of 781
Sign every commit38% signed today +3.0 → 36.1 D · #739 of 781

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships IBKR Portfolio Builder and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Partly signed

github.com/adwiteeymauriya/ibkr-portfolio-builder-mcp, MIT, last pushed 2026-06-08. 38% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
Review and release Weak

OpenSSF Scorecard rates the repository's practices 2.1/10 (scanned Oct 7, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection3
- Signed Releasesn/a
- Dangerous Workflow0
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 0

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0
Published packages None

No registry package. IBKR Portfolio Builder is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

2026-08-27 OSSF Scorecard: 2.3/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

GitHub repository data
Package downloads (missing)
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues IBKR Portfolio Builder’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How IBKR Portfolio Builder compares in MCP Servers

#759 HAL 33.6 +0.5
#760 MCP Explorium 33.5 +0.4
#761 IBKR Portfolio Builder 33.1 this agent
#762 Academia MCP 32.6 −0.5
#763 Banco MCP 32.0 −1.1

Bars show each HVTrust score; the tick marks IBKR Portfolio Builder’s 33.1.

Where the 33.1 comes from

HVTrust dimensions vs the MCP Servers average

33.1 / 100 · 100.0% confidence

IBKR Portfolio Builder MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

4.6 / 25

5.9 below avg 10.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.7 below avg 13.5

Transparency50% declared license · 50% OSSF Scorecard

10.3 / 17

2.0 below avg 12.3

Maintenance60% last-push freshness · 40% commit activity

3.3 / 20

9.0 below avg 12.3

AdoptionLog-scaled stars · package downloads

3.1 / 20

4.3 below avg 7.4

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-10-09

Rank Moved

Rank dropped 14 spots (#1274 → #1288)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank dropped 189 spots (#1058 → #1247)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 2.1/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Refresh maintenance signals The repo was last pushed 131 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for IBKR Portfolio Builder View MCP Servers Report missing data

17.4

Activity sub-score · out of 100

#761

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-09-29 2026-10-17

Activity & Reach

Stars

Forks

Last Push

2026-06-08

131 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #1314

Analysis

Activity Inputs

17.4 / 100

StarsRepository reach

7.8 / 30

FreshnessLast push recency

6.8 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

2.8 / 20

Common questions about IBKR Portfolio Builder

Public trust evidence for IBKR Portfolio Builder is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does IBKR Portfolio Builder publish package provenance?

No published build provenance is currently detected for IBKR Portfolio Builder. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does IBKR Portfolio Builder have an OpenSSF Scorecard?

IBKR Portfolio Builder has an OpenSSF Scorecard score of 2.1/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is IBKR Portfolio Builder actively maintained?

Slowing down. Last push was 131 days ago — keep an eye on whether activity resumes.

What license does IBKR Portfolio Builder use?

IBKR Portfolio Builder ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are IBKR Portfolio Builder's commits signed?

38% of the last 100 commits to IBKR Portfolio Builder are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

IBKR Portfolio Builder appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to IBKR Portfolio Builder's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-06

Activity Went Stale

No commits for 90 days

Maintain IBKR Portfolio Builder?

For maintainers

HVTrust scores IBKR Portfolio Builder from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-10-09

Rank Moved

Rank dropped 14 spots (#1274 → #1288)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank dropped 189 spots (#1058 → #1247)

2026-09-23

HVTrust Changed

HVTrust up 11.5pts (23.2 → 34.7)

2026-09-22

Newly Listed

First tracked at rank #1058

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-09

Rank Moved

Rank dropped 12 spots (#1203 → #1215)

2026-09-08

Rank Moved

Rank dropped 14 spots (#1189 → #1203)

2026-09-07

Rank Moved

Rank dropped 17 spots (#1172 → #1189)

2026-09-06

Activity Went Stale

No commits for 90 days

2026-09-06

Rank Moved

Rank dropped 17 spots (#1155 → #1172)

2026-09-05

Rank Moved

Rank dropped 33 spots (#1122 → #1155)

2026-09-04

Rank Moved

Rank dropped 20 spots (#1102 → #1122)

2026-09-03

Rank Moved

Rank dropped 51 spots (#1051 → #1102)

2026-09-02

Rank Moved

Rank dropped 46 spots (#1005 → #1051)

2026-09-01

Rank Moved

Rank dropped 43 spots (#962 → #1005)

2026-08-31

Rank Moved

Rank dropped 33 spots (#929 → #962)

2026-08-30

Rank Moved

Rank dropped 45 spots (#884 → #929)

2026-08-29

Rank Moved

Rank dropped 48 spots (#836 → #884)

2026-08-28

Rank Moved

Rank dropped 26 spots (#810 → #836)

2026-08-27

Scorecard Added

OSSF Scorecard: 2.3/10

2026-08-27

Rank Moved

Rank rose 437 spots (#1247 → #810)

2026-08-27

HVTrust Changed

HVTrust up 20.4pts (16.5 → 36.9)

2026-08-26

Rank Moved

Rank dropped 30 spots (#1217 → #1247)

2026-08-16

Rank Moved

Rank dropped 26 spots (#1185 → #1211)

2026-08-12

Rank Moved

Rank dropped 24 spots (#1158 → #1182)

2026-08-10

Rank Moved

Rank dropped 68 spots (#1088 → #1156)

2026-08-08

Newly Listed

First tracked at rank #1106

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/ibkr-portfolio-builder.svg)](https://hvtracker.net/agents/ibkr-portfolio-builder)
            
HTML:
            <a href="https://hvtracker.net/agents/ibkr-portfolio-builder"><img src="https://hvtracker.net/badge/ibkr-portfolio-builder.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON

IBKR Portfolio Builder

How IBKR Portfolio Builder could raise its score

Chain of custody

Source Partly signed

Review and release Weak

Published packages None

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How IBKR Portfolio Builder compares in MCP Servers

Where the 33.1 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about IBKR Portfolio Builder

AI agent surface

Maintain IBKR Portfolio Builder?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers